Triple
T14185663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | De Akkers |
E351567
|
entity |
| Predicate | servesAsTerminus |
P388
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [De Akkers, servesAsTerminus, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesAsTerminus Context triple: [De Akkers, servesAsTerminus, yes]
-
A.
locatedAtTerminusOf
Indicates that one entity is situated at the end point or final terminus of another entity, such as a route, line, or path.
-
B.
hasTerminusRole
Indicates that an entity participates in something specifically in the capacity of a terminus or endpoint role.
-
C.
formerTerminusFor
Indicates that a location once served as the endpoint or final stop of a route, line, or service, but no longer holds that status.
-
D.
terminus
chosen
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
E.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
- 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_69d8278834a08190b0f1784e58d7b99c |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61cd5778819092a03597bcdcc182 |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05baed64819096590e5618a3a8ed |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 1:03 a.m.