Triple
T37028284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruby (gemstone) |
E916415
|
entity |
| Predicate | historicallyFamousLocality |
P201083
|
FINISHED |
| Object | Mogok Valley |
—
|
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: Mogok Valley | Statement: [Ruby (gemstone), historicallyFamousLocality, Mogok Valley]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyFamousLocality Context triple: [Ruby (gemstone), historicallyFamousLocality, Mogok Valley]
-
A.
heritageOfLocation
Indicates that a particular location possesses or is associated with a recognized cultural, historical, or natural heritage.
-
B.
historicallyLinkedPlace
chosen
Indicates that one place has a significant historical connection or association with another place.
-
C.
historicallyImportantCenter
Indicates that a place has served as a significant focal point of historical events, activities, or influence.
-
D.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
E.
heritageLocation
Indicates that a location is recognized or designated as having cultural, historical, or natural heritage significance in relation to something.
- 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_69f76e92c7648190bcfa277f64c71a21 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0174e8b5b481908bf0c6d3d5b0f3b6 |
completed | May 11, 2026, 6:19 a.m. |
| PD | Predicate disambiguation | batch_6a01748d65248190ac3d9adfa9d0b274 |
completed | May 11, 2026, 6:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.