Triple
T22583118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian obelisk |
E544615
|
entity |
| Predicate | inscriptionsTypicallyRecord |
P9127
|
FINISHED |
| Object | pharaoh's names |
—
|
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: pharaoh's names | Statement: [Egyptian obelisk, inscriptionsTypicallyRecord, pharaoh's names]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inscriptionsTypicallyRecord Context triple: [Egyptian obelisk, inscriptionsTypicallyRecord, pharaoh's names]
-
A.
notableInscriptionBy
Indicates that an inscription of particular note or significance on an entity was created, authored, or carved by a specified agent.
-
B.
inscriptionsFoundAt
Indicates that inscriptions are discovered or located at a particular place or site.
-
C.
mainContentOfInscriptions
chosen
Indicates that something represents the primary textual or symbolic content conveyed by a set of inscriptions.
-
D.
materialTypicallyInscribedOn
Indicates the material that is most commonly used as the surface or medium on which something is inscribed.
-
E.
inscriptionTranslation
Indicates that a provided text expresses the translated content of a specific inscription.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f15ff26d6481908cc058f8c4b87e75 |
completed | April 29, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69ee626e6bb08190ada4dd8b48cc0c43 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:53 p.m.