Triple
T4049060
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ryde, Isle of Wight |
E84138
|
entity |
| Predicate | hasPierFunction |
P53816
|
FINISHED |
| Object | transport link |
—
|
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: transport link | Statement: [Ryde, Isle of Wight, hasPierFunction, transport link]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPierFunction Context triple: [Ryde, Isle of Wight, hasPierFunction, transport link]
-
A.
hasPier
Indicates that a location or structure possesses or includes a pier as part of its features.
-
B.
pierOpened
Indicates that a pier has been officially opened or made available for use, typically at a specific time or event.
-
C.
hasHubFunction
Indicates that an entity serves as a central hub or coordinating point for certain activities, connections, or functions within a system.
-
D.
hasPortal
Indicates that one entity possesses or provides access to a portal connecting to another location or entity.
-
E.
hasPilotis
Indicates that a building or structure is elevated on pilotis (supporting columns or stilts), rather than resting directly on the ground.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb82d1a08190aa8c5c48d368b58b |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef98ed84c81909dc86097df4afd4f |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:37 p.m.