Triple
T22583101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian obelisk |
E544615
|
entity |
| Predicate | oftenErectedBy |
P25865
|
FINISHED |
| Object | pharaohs |
—
|
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: pharaohs | Statement: [Egyptian obelisk, oftenErectedBy, pharaohs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenErectedBy Context triple: [Egyptian obelisk, oftenErectedBy, pharaohs]
-
A.
erected
Indicates that one entity caused a structure or object to be built or put upright, typically in a deliberate and often permanent manner.
-
B.
erectedBy
chosen
Indicates that something (such as a structure, monument, or installation) was constructed, set up, or raised by a particular agent or entity.
-
C.
placeBuilt
Indicates that a structure or facility was constructed at a specific location.
-
D.
mayErect
Indicates that one entity is permitted or authorized to construct or put up another entity (such as a structure or installation).
-
E.
eraOfManyBuildings
Indicates a time period during which many buildings were constructed or existed.
- 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.