Triple
T31067111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lysimachia |
E791706
|
entity |
| Predicate | builtOnOrNearSiteOf |
P21298
|
FINISHED |
| Object | Cardia |
—
|
NE NERFINISHED |
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: Cardia | Statement: [Lysimachia, builtOnOrNearSiteOf, Cardia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtOnOrNearSiteOf Context triple: [Lysimachia, builtOnOrNearSiteOf, Cardia]
-
A.
rebuiltOnSiteOf
Indicates that a structure was reconstructed or newly built on the same physical location where an earlier structure once stood.
-
B.
builtNear
chosen
Indicates that one entity was constructed at a location geographically close to another entity.
-
C.
believedToBeSiteOf
Indicates that something is thought or assumed, though not definitively proven, to be the location where a particular event, structure, or phenomenon occurred or existed.
-
D.
isSiteOf
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
E.
formerSiteOf
Indicates that a location previously hosted or contained something (such as a structure, organization, or event) that is no longer present there.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69dfdda708190be290c7bec205445 |
completed | May 3, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:01 p.m.