Triple
T26268778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Lebanon |
E657059
|
entity |
| Predicate | isAboutLocation |
P15985
|
FINISHED |
| Object | Lebanon |
—
|
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: Lebanon | Statement: [The Lebanon, isAboutLocation, Lebanon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAboutLocation Context triple: [The Lebanon, isAboutLocation, Lebanon]
-
A.
likelyLocatedIn
Indicates that an entity is probably situated within or associated with a particular location, though not with absolute certainty.
-
B.
hasLocationRole
Indicates that an entity holds or plays a specific role in relation to a particular location (e.g., origin, destination, storage site, or operational area).
-
C.
refersToLocation
chosen
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
D.
agingLocation
Indicates the place where an entity undergoes an aging process or is stored to age over time.
-
E.
timeLocatedIn
Indicates that an event, state, or entity occurs, exists, or is valid within a specified time or temporal interval.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69f60e2fb90c8190a05e458ca3cccadc |
completed | May 2, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 9:12 p.m.