Triple
T20319596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mallaig–Armadale ferry route |
E492173
|
entity |
| Predicate | portTypeAtArmadale |
P139654
|
FINISHED |
| Object | rural ferry terminal |
—
|
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: rural ferry terminal | Statement: [Mallaig–Armadale ferry route, portTypeAtArmadale, rural ferry terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portTypeAtArmadale Context triple: [Mallaig–Armadale ferry route, portTypeAtArmadale, rural ferry terminal]
-
A.
portLocation
Indicates that a port is geographically situated at or associated with a specific location.
-
B.
portAlsoKnownAs
Indicates that a port is referred to by an alternative name or alias.
-
C.
typeOfPortFacility
Indicates that one port facility is classified as a specific type or category of port facility in relation to another.
-
D.
portSystem
Indicates that one system serves as a port or interface through which another system connects, communicates, or transfers data or resources.
-
E.
portTypeOperated
Indicates that one entity operates, manages, or runs the specified type of port associated with another entity.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778abd14819098a01fd32217fdde |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b23a0788190bf1853ef5b81823f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 16, 2026, 11:20 a.m.