Triple
T35880807
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artouz |
E1037500
|
entity |
| Predicate | geographicDirectionFromDamascus |
P191841
|
FINISHED |
| Object | southwest |
—
|
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: southwest | Statement: [Artouz, geographicDirectionFromDamascus, southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geographicDirectionFromDamascus Context triple: [Artouz, geographicDirectionFromDamascus, southwest]
-
A.
geographicalDirectionFromConstantinople
Indicates that one place is located in a specified cardinal or intercardinal direction relative to Constantinople.
-
B.
distanceFromDamascus
Indicates the measured distance between a given location and the city of Damascus.
-
C.
geographicDirectionFromAthens
Indicates the cardinal or intercardinal geographic direction in which one place is located relative to Athens.
-
D.
directionFromBeirut
Indicates the cardinal or relative compass direction in which one entity is located when measured from Beirut.
-
E.
elevationRelativeToDamascus
Indicates the relative elevation difference between a given location and the city of Damascus, specifying how much higher or lower the location is compared to Damascus.
- 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_69f76e1f4d748190bb55594d8441d70e |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcec5f8b448190b48330a19b462d24 |
completed | May 7, 2026, 7:47 p.m. |
| PD | Predicate disambiguation | batch_69fceaf1e23881908ca24160a638e329 |
completed | May 7, 2026, 7:41 p.m. |
| PDg | Predicate description generation | batch_69fcec5e560481909cd710b88897e833 |
completed | May 7, 2026, 7:47 p.m. |
Created at: May 3, 2026, 4:06 p.m.