Triple
T26086658
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panjdeh Oasis |
E658000
|
entity |
| Predicate | nearbyCityHistorical |
P72879
|
FINISHED |
| Object | Merv |
—
|
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: Merv | Statement: [Panjdeh Oasis, nearbyCityHistorical, Merv]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearbyCityHistorical Context triple: [Panjdeh Oasis, nearbyCityHistorical, Merv]
-
A.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
-
B.
historicalServiceNear
Indicates that a historical service or event occurred in close spatial proximity to a specified location or entity.
-
C.
focusCityHistory
Indicates that there is a historical or context-defining relationship between a focal city and its past events, developments, or status.
-
D.
hasNearbyHistoricArea
chosen
Indicates that one entity is located close to another entity that is designated as a historic area.
-
E.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 26, 2026, 7:43 p.m.