Triple
T26512064
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giza royal family |
E669709
|
entity |
| Predicate | connectedToMonument |
P180926
|
FINISHED |
| Object | Great Pyramid of Giza |
—
|
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: Great Pyramid of Giza | Statement: [Giza royal family, connectedToMonument, Great Pyramid of Giza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedToMonument Context triple: [Giza royal family, connectedToMonument, Great Pyramid of Giza]
-
A.
appliesToMonument
Indicates that something (such as a rule, status, or attribute) is relevant or applicable specifically to a monument.
-
B.
hasWorkOnMonument
Indicates that an entity has created, contributed to, or performed work on a particular monument.
-
C.
usedInMonument
Indicates that something serves as a material, component, or element incorporated into the construction or design of a monument.
-
D.
hasMarkerOrMonument
Indicates that something possesses or is associated with a physical marker or monument commemorating it.
-
E.
hasScheduledMonument
Indicates that an entity is associated with, or contains, a site or structure officially designated as a scheduled monument.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f75dc25fa08190b371faf36d9fb72c |
completed | May 3, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69f758586534819083e91172f4bf5098 |
completed | May 3, 2026, 2:14 p.m. |
| PDg | Predicate description generation | batch_69f75dc140c4819085063d6c4c36ca61 |
completed | May 3, 2026, 2:37 p.m. |
Created at: April 27, 2026, 1:21 a.m.