Triple
T565469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charioteer of Delphi |
E13541
|
entity |
| Predicate | museumCollection |
P3831
|
FINISHED |
| Object | Archaeological Museum of Delphi permanent collection |
—
|
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: Archaeological Museum of Delphi permanent collection | Statement: [Charioteer of Delphi, museumCollection, Archaeological Museum of Delphi permanent collection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: museumCollection Context triple: [Charioteer of Delphi, museumCollection, Archaeological Museum of Delphi permanent collection]
-
A.
majorMuseum
Indicates that a museum holds significant importance or prominence, typically due to its size, collections, reputation, or cultural impact.
-
B.
museumAt
chosen
Indicates that an entity (such as an exhibit, artifact, or event) is located at or associated with a particular museum.
-
C.
museumCity
Indicates the city in which a given museum is located.
-
D.
hasMuseumType
Indicates that an entity is classified as a museum of a specific type or category.
-
E.
museOf
Indicates that one entity serves as the source of artistic or intellectual inspiration for another.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49a74793481908fee3baff0b1d348 |
completed | March 1, 2026, 7:58 p.m. |
| PD | Predicate disambiguation | batch_69a494c044648190a98589ab18935216 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:32 p.m.