Triple
T12168042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Lebanon |
E289884
|
entity |
| Predicate | bordersDefinedIn |
P103116
|
FINISHED |
| Object | 1920 |
—
|
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: 1920 | Statement: [Greater Lebanon, bordersDefinedIn, 1920]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bordersDefinedIn Context triple: [Greater Lebanon, bordersDefinedIn, 1920]
-
A.
borderDefinedBy
Indicates that the boundary or limit of one entity is determined, shaped, or delineated by another entity.
-
B.
bordersVia
Indicates that two entities share a boundary or border that is specifically established, defined, or mediated through a particular intermediate feature, route, or medium.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
bordersEntity
Indicates that one entity shares a common boundary or border with another entity.
-
E.
bordersJurisdiction
Indicates that one jurisdiction shares a boundary or border with another jurisdiction.
- 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_69d6ab4d6c00819095a9a7c35de83cfb |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d91621ca6c81908365732f361aef13 |
completed | April 10, 2026, 3:24 p.m. |
| PD | Predicate disambiguation | batch_69d9150e85348190b9b47cda4a17dcd0 |
completed | April 10, 2026, 3:19 p.m. |
| PDg | Predicate description generation | batch_69d916165c708190bf0745e125589f46 |
completed | April 10, 2026, 3:24 p.m. |
Created at: April 8, 2026, 9:50 p.m.