Triple
T20052604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maaloula |
E499240
|
entity |
| Predicate | distanceFromDamascus |
P138520
|
FINISHED |
| Object | approximately 50–60 km |
—
|
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: approximately 50–60 km | Statement: [Maaloula, distanceFromDamascus, approximately 50–60 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromDamascus Context triple: [Maaloula, distanceFromDamascus, approximately 50–60 km]
-
A.
distanceToAleppo
Indicates the spatial distance between a given entity and the location of Aleppo.
-
B.
distanceFromBeirut
Indicates the measured spatial distance between a given entity’s location and the city of Beirut.
-
C.
distanceFromSyriaBorder
Indicates the measured spatial separation between a location and the nearest point on Syria’s national border.
-
D.
distanceFromBaghdad
Indicates the spatial distance between a given location or entity and the city of Baghdad.
-
E.
distanceFromBethlehem
Indicates the spatial distance between a given location and Bethlehem.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6633043a481908359ad232607182a |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc20888819083c9118a09d0d2dc |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 3:38 p.m.