Triple
T22659915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tripoli Eyalet |
E559633
|
entity |
| Predicate | encompassedRegion |
P146166
|
FINISHED |
| Object | northern Lebanon |
—
|
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: northern Lebanon | Statement: [Tripoli Eyalet, encompassedRegion, northern Lebanon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: encompassedRegion Context triple: [Tripoli Eyalet, encompassedRegion, northern Lebanon]
-
A.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
-
B.
roughlyEncompassed
chosen
Indicates that one entity includes or surrounds another in an approximate or imprecise manner, without strict or exact boundaries.
-
C.
formationRegion
Indicates the place or area where something originates, is created, or comes into being.
-
D.
enclosesArea
Indicates that one entity surrounds and contains a bounded region of space occupied or defined by another.
-
E.
dominatedRegion
Indicates that one entity exercises controlling power or authority over a particular geographic or conceptual region.
- 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_69e2454a158c819093b8e35f5045efb6 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1765dc9088190b022ac564a8b5c26 |
completed | April 29, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:07 p.m.