Triple
T31519447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Langeland Bridge |
E804164
|
entity |
| Predicate | endpointOnLangeland |
P89729
|
FINISHED |
| Object | Rudkøbing, Langeland |
—
|
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: Rudkøbing, Langeland | Statement: [Langeland Bridge, endpointOnLangeland, Rudkøbing, Langeland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endpointOnLangeland Context triple: [Langeland Bridge, endpointOnLangeland, Rudkøbing, Langeland]
-
A.
endpointOnPeninsula
chosen
Indicates that one endpoint of an object, path, or feature lies on or within the bounds of a peninsula.
-
B.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
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.
distanceFromLongyearbyen
Indicates the measured distance between a given location and Longyearbyen.
-
E.
easternTerminusLocatedOn
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 9:55 p.m.