Triple
T21516686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazmieh |
E530860
|
entity |
| Predicate | directionFromBeirut |
P144686
|
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: [Hazmieh, directionFromBeirut, southeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromBeirut Context triple: [Hazmieh, directionFromBeirut, southeast]
-
A.
drivingTimeFromBeirut
Indicates the amount of time it takes to drive from Beirut to a given location.
-
B.
distanceFromBeirut
Indicates the measured spatial distance between a given entity’s location and the city of Beirut.
-
C.
directionFromJerusalem
Indicates the cardinal or relative compass direction of one place or object as measured outward starting from Jerusalem.
-
D.
directionFromParis
Indicates the cardinal or relative compass direction of an entity as measured from Paris toward that entity.
-
E.
directionFromAmman
Indicates the cardinal or relative compass direction in which one entity is located from Amman.
- 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_69e0c45d95a081908e7962ad215da746 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee814278e08190a66d516bed0726b5 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e6320043bc81909417c41a718652ba |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e6386c5a4481909c37f7de7e9fc025 |
completed | April 20, 2026, 2:30 p.m. |
Created at: April 16, 2026, 6:25 p.m.