Triple
T5773139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tura, Egypt |
E127374
|
entity |
| Predicate | stoneQuality |
P66351
|
FINISHED |
| Object | high-quality |
—
|
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: high-quality | Statement: [Tura, Egypt, stoneQuality, high-quality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stoneQuality Context triple: [Tura, Egypt, stoneQuality, high-quality]
-
A.
stateGemstone
Indicates a relationship where a state is officially associated with or designated a particular gemstone.
-
B.
stoneColor
Indicates that one entity has a particular color attribute associated with a stone.
-
C.
rockTypeMarketedAs
Indicates that a particular rock type is promoted or advertised under a specific commercial or trade name.
-
D.
stoneFitting
Indicates that one stone is shaped or positioned so that it fits securely and appropriately with another stone or within a designated stone structure.
-
E.
quarriedFor
Indicates that a location or source is excavated or mined in order to obtain a particular material or resource.
- 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_69c00834f6308190851b0abeddd8ed7e |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02acb12c081908e4beee4a957f9f9 |
completed | March 22, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69c021d0c6088190ba670ddcdbf5ca3e |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c02ac9603481909e3fa295d7904a15 |
completed | March 22, 2026, 5:45 p.m. |
Created at: March 22, 2026, 3:50 p.m.