Triple
T3546559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sanctuary of Olympia |
E75009
|
entity |
| Predicate | foundedAsSanctuary |
P364
|
FINISHED |
| Object | in the late 2nd millennium BCE |
—
|
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: in the late 2nd millennium BCE | Statement: [Sanctuary of Olympia, foundedAsSanctuary, in the late 2nd millennium BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundedAsSanctuary Context triple: [Sanctuary of Olympia, foundedAsSanctuary, in the late 2nd millennium BCE]
-
A.
foundedAs
chosen
Indicates the original name or form under which an organization, institution, or entity was first established.
-
B.
hadSanctuaryOf
Indicates that an entity possessed or hosted a sanctuary dedicated to another entity.
-
C.
foundedUnder
Indicates that an entity was established or created during the tenure, authority, or jurisdiction of another entity (such as a leader, regime, or governing body).
-
D.
foundedFor
Indicates that an entity was established or created specifically to serve, support, or benefit another entity or purpose.
-
E.
foundedFrom
Indicates that an entity was established or originated starting from a particular source, place, or prior entity.
- 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_69ad85d33c6c819081d5ac1df13b5680 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adbfcf64488190af8452308734028c |
completed | March 8, 2026, 6:28 p.m. |
| PD | Predicate disambiguation | batch_69adae15749881909b847c6ca73c934e |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:20 p.m.