Triple
T37514180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caldeum Desert |
E932590
|
entity |
| Predicate | notableNearbyLocation |
P19575
|
FINISHED |
| Object | city of Caldeum |
—
|
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: city of Caldeum | Statement: [Caldeum Desert, notableNearbyLocation, city of Caldeum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableNearbyLocation Context triple: [Caldeum Desert, notableNearbyLocation, city of Caldeum]
-
A.
notableNearbySite
chosen
Indicates that one entity is a significant or noteworthy site located close to another entity.
-
B.
nearbyLocation
Indicates that one location is situated close to another location in physical space.
-
C.
typicalNearbyLandmarks
Indicates that certain landmarks are commonly found in the vicinity of a given place or location.
-
D.
notableLocation
Indicates that a location is especially significant, prominent, or noteworthy in relation to the subject.
-
E.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
- 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_69f76ec730988190b5aa4f9cb9afd518 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1553e08190bb7424c448cb1f33 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:17 p.m.