Triple
T33998381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R11 |
E871738
|
entity |
| Predicate | terminusTowardsBorder |
P159755
|
FINISHED |
| Object | French border |
—
|
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: French border | Statement: [R11, terminusTowardsBorder, French border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusTowardsBorder Context triple: [R11, terminusTowardsBorder, French border]
-
A.
terminusTowards
chosen
Indicates that one entity serves as the endpoint or directional terminus oriented toward another entity.
-
B.
hasBorderTerminus
Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
-
C.
borderTerminus
Indicates the endpoint location where a border between two areas or entities begins or ends.
-
D.
borderTypeAtTerminusB
Indicates the type or classification of the border present at the second (B) endpoint of a defined boundary or connection.
-
E.
terminusAdjacentTo
Indicates that one terminus (end point) of a route, line, or feature is directly next to or immediately bordering another terminus.
- 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 1, 2026, 1:50 a.m.