Triple
T34772217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Glenorchy |
E1002392
|
entity |
| Predicate | destinationInOperationPedestal |
P164064
|
FINISHED |
| Object | Malta |
—
|
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: Malta | Statement: [SS Glenorchy, destinationInOperationPedestal, Malta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationInOperationPedestal Context triple: [SS Glenorchy, destinationInOperationPedestal, Malta]
-
A.
destinationFeature
chosen
Indicates the feature, place, or element that serves as the endpoint or target location of a movement, transfer, or directed relation.
-
B.
hasTramDestination
Indicates that a tram route or service goes to or terminates at a specified destination.
-
C.
isGroundTransportHubFor
Indicates that a location functions as a central node or facility for organizing, coordinating, or serving ground-based transportation for another place or set of routes.
-
D.
transportGoal
Indicates that an entity has the objective or intended outcome of moving or conveying something or someone from one place to another.
-
E.
hasConveyorBeltDestination
Indicates that an item on a conveyor belt is intended to be transported to a specific target location or endpoint.
- 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_69f76db20dac8190b1e8d0ca4dc1d59f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.