Triple
T33007042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belfast–Liverpool ferry route |
E844530
|
entity |
| Predicate | hasTerminalCity |
P26386
|
FINISHED |
| Object | Belfast |
—
|
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: Belfast | Statement: [Belfast–Liverpool ferry route, hasTerminalCity, Belfast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminalCity Context triple: [Belfast–Liverpool ferry route, hasTerminalCity, Belfast]
-
A.
hasUrbanTerminus
Indicates that a route, line, or service ends or terminates within an urban area or city.
-
B.
hasTargetCity
Indicates that something is directed toward, intended for, or specifically associated with a particular city as its target.
-
C.
hasEndpointCity
chosen
Indicates that a route, connection, or path terminates at a particular city as one of its endpoints.
-
D.
terminusCityIsPort
Indicates that the city where a route or journey ends functions as a port.
-
E.
hasGatewayCity
Indicates that one place serves as the primary gateway city (main entry or transit hub) for accessing another place.
- 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_69f3494e59f08190b9127c693e5c7e8f |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd5f29b1988190877764ef2a399c7f |
completed | May 8, 2026, 3:57 a.m. |
| PD | Predicate disambiguation | batch_69fd5e30194c819085b5ce586122ab37 |
completed | May 8, 2026, 3:53 a.m. |
Created at: May 1, 2026, 1:23 a.m.