Triple
T8386665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arthur Evans |
E197832
|
entity |
| Predicate | coinvented |
P1858
|
FINISHED |
| Object | term "Minoan" for the Bronze Age civilization of Crete |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: term "Minoan" for the Bronze Age civilization of Crete | Statement: [Arthur Evans, coinvented, term "Minoan" for the Bronze Age civilization of Crete]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coinvented Context triple: [Arthur Evans, coinvented, term "Minoan" for the Bronze Age civilization of Crete]
-
A.
co-discoveredWith
Indicates that two or more entities jointly discovered the same object, phenomenon, or finding.
-
B.
invention
Indicates that one entity is the creator or originator of another entity, typically a device, method, or idea.
-
C.
coInventorWith
chosen
Indicates that two or more entities jointly invented or created the same invention.
-
D.
wasInventedBy
Indicates that something (typically an object, concept, or process) was created or brought into existence by a particular inventor or originator.
-
E.
coCreator
Indicates that two or more entities jointly created or produced something together.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ca82f749388190bffbea6dfb509016 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80e1bcdc81909111aa33ee996e0a |
completed | March 31, 2026, 8:08 a.m. |
| PD | Predicate disambiguation | batch_69cb70cfe82881909fe374ba52649e84 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:03 p.m.