Triple
T31519448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langeland Bridge |
E804164
|
entity |
| Predicate | endpointOnSiø |
P172571
|
FINISHED |
| Object | Siø, Svendborg Municipality |
—
|
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: Siø, Svendborg Municipality | Statement: [Langeland Bridge, endpointOnSiø, Siø, Svendborg Municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endpointOnSiø Context triple: [Langeland Bridge, endpointOnSiø, Siø, Svendborg Municipality]
-
A.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
B.
endpointFeature
Indicates that a particular feature, capability, or characteristic is associated with, provided by, or available at a specific endpoint.
-
C.
endpointOnLake
Indicates that one end of a linear feature (such as a road, path, or boundary) terminates at or directly on the shore of a lake.
-
D.
endpointInclusion
Indicates that one endpoint is contained within or is part of another endpoint or endpoint set.
-
E.
endPointExample
Indicates that something serves as a representative or illustrative instance of a particular endpoint.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ac1ed23c8190ace57ffc9d8a3dc6 |
completed | May 3, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69f6aa1e84b88190b025f6ca40f17a8a |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aba8fba48190bc1a17117244cae1 |
completed | May 3, 2026, 1:58 a.m. |
Created at: April 30, 2026, 9:55 p.m.