Triple
T21170653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Message of the Sphinx |
E521681
|
entity |
| Predicate | positionOnDatingOfSphinx |
P143145
|
FINISHED |
| Object | supports a date around 10,500 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: supports a date around 10,500 BCE | Statement: [The Message of the Sphinx, positionOnDatingOfSphinx, supports a date around 10,500 BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionOnDatingOfSphinx Context triple: [The Message of the Sphinx, positionOnDatingOfSphinx, supports a date around 10,500 BCE]
-
A.
positionOnMyth
Indicates the relative stance or viewpoint an entity holds regarding a particular myth.
-
B.
positionOnAcropolis
Indicates that something is located on or occupies a position on the Acropolis.
-
C.
pyramidLocation
Indicates that one entity is located at, in, or on a pyramid or a specific position relative to a pyramid.
-
D.
positionInTemple
Indicates the specific location or role an entity occupies within a temple.
-
E.
positionOnIdentity
Indicates a stance, view, or opinion that an entity holds regarding identity-related issues or characteristics.
- F. None of above. chosen
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_69e0b50e30748190b186824a206d39b9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e72712893081908e394ccc7e0cbb53 |
completed | April 21, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
| PDg | Predicate description generation | batch_69e5f993240c8190847c0b08e65726c8 |
completed | April 20, 2026, 10:01 a.m. |
Created at: April 16, 2026, 3 p.m.