Triple
T32471814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qarchak |
E829867
|
entity |
| Predicate | geographicDirectionFromTehran |
P180859
|
FINISHED |
| Object | southeast |
—
|
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: southeast | Statement: [Qarchak, geographicDirectionFromTehran, southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicDirectionFromTehran Context triple: [Qarchak, geographicDirectionFromTehran, southeast]
-
A.
directionFromTehran
chosen
Indicates the cardinal or relative compass direction in which one entity is located from Tehran.
-
B.
distanceFromTehran
Indicates the spatial distance between a given entity and the city of Tehran.
-
C.
directionFromMecca
Indicates the geographic direction in which one entity lies relative to Mecca as the reference point.
-
D.
geographicDirectionFromRegionalCapital
Indicates the cardinal or intercardinal direction in which a place is located relative to its regional capital.
-
E.
geographicDirectionFromTurin
Indicates the geographic direction in which one place lies relative to the location of Turin.
- 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_69f3491ee87c81908cbf5890079c2af6 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 12:57 a.m.