Triple
T9495754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tura |
E228999
|
entity |
| Predicate | quarriesUsedFor |
P71689
|
FINISHED |
| Object | pyramids at Giza |
—
|
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: pyramids at Giza | Statement: [Tura, quarriesUsedFor, pyramids at Giza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: quarriesUsedFor Context triple: [Tura, quarriesUsedFor, pyramids at Giza]
-
A.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
-
B.
materialFromQuarriesUsedFor
chosen
Indicates that material extracted from quarries is used for a particular purpose, project, or object.
-
C.
quarriedNear
Indicates that a material or resource was extracted from a quarry located close to a specified place or feature.
-
D.
hasQuarries
Indicates that one entity possesses, contains, or is associated with one or more quarries used for extracting stone or similar materials.
-
E.
quarryingWasImportantFor
Indicates that the activity of quarrying played a significant or central role for the referenced entity, such as in its economy, development, or functioning.
- 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_69ca84753660819098e8d416e89e26ae |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd95eb87b081908fc7255598cd9a24 |
completed | April 1, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69cca5651a588190a3cfebe249a223e5 |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 7:56 p.m.