Triple
T29033439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gordion |
E737788
|
entity |
| Predicate | notableTumulus |
P133766
|
FINISHED |
| Object | Tumulus MM |
E1012115
|
NE 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: Tumulus MM | Statement: [Gordion, notableTumulus, Tumulus MM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableTumulus Context triple: [Gordion, notableTumulus, Tumulus MM]
-
A.
tombNotableFeature
Indicates that a tomb is distinguished or recognized for a particular notable feature or characteristic.
-
B.
hasNotableBurials
Indicates that a place, typically a cemetery or burial site, contains the graves or remains of individuals considered notable or significant.
-
C.
burialComplexOf
Indicates that one entity is the burial complex associated with, containing, or dedicated to another entity (typically the person or group interred there).
-
D.
hasTombDesignation
Indicates that an entity has been assigned a specific formal designation or identifier for its tomb.
-
E.
hasBurialMonumentType
chosen
Indicates that an entity is associated with a burial whose monument is of a specified type.
- F. None of above.
Provenance (4 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0204dafcc08190868a6f3eab162505 |
completed | May 11, 2026, 4:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2505d9c09c81908bf3d87590cbdc3d |
completed | June 7, 2026, 5:47 a.m. |
| PD | Predicate disambiguation | batch_6a0202dc60348190a140bb9da906f5b6 |
completed | May 11, 2026, 4:25 p.m. |
Created at: April 28, 2026, 9:57 a.m.