Triple
T27214198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Beirut |
E684090
|
entity |
| Predicate | separationLine |
P21958
|
FINISHED |
| Object | Green Line (Beirut) |
—
|
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: Green Line (Beirut) | Statement: [West Beirut, separationLine, Green Line (Beirut)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separationLine Context triple: [West Beirut, separationLine, Green Line (Beirut)]
-
A.
divisionLine
chosen
Indicates a boundary or separating line that divides one area, group, or portion from another.
-
B.
rulingLine
Indicates that one entity is the ruling or governing lineage, dynasty, or family over another entity (such as a territory, people, or polity).
-
C.
spaceLine
Indicates a relationship where entities are connected or arranged along a line within a spatial context or coordinate system.
-
D.
providesSeparationFor
Indicates that one entity serves to divide, isolate, or keep another entity apart from something else.
-
E.
separators
Indicates that one entity divides, distinguishes, or creates a boundary between two or more other entities.
- 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_69eefad339a08190aeacb2a198f1a39b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f6383625cc8190aa223d8ef655743c |
completed | May 2, 2026, 5:45 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 9:40 a.m.