Triple
T31396498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PS Waverley |
E800876
|
entity |
| Predicate | originalServiceRole |
P202777
|
FINISHED |
| Object | Clyde passenger steamer |
—
|
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: Clyde passenger steamer | Statement: [PS Waverley, originalServiceRole, Clyde passenger steamer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalServiceRole Context triple: [PS Waverley, originalServiceRole, Clyde passenger steamer]
-
A.
primaryServiceRole
Indicates the main or most important functional role that a service performs in relation to other entities or processes.
-
B.
originalServiceBranch
Indicates the military or organizational service branch in which an individual initially served or was first enlisted.
-
C.
enteredServiceRole
Indicates that an entity has begun serving in a particular role, position, or capacity.
-
D.
serverRole
Indicates the functional role or responsibility that a server has within a system or network.
-
E.
startupRole
Indicates that an entity holds a specific role or position within a startup organization.
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_6a00b7fb90f881908f73edf2be8cc3a5 |
completed | May 10, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_6a00b75593d08190b3e76191cd79cdec |
completed | May 10, 2026, 4:50 p.m. |
| PDg | Predicate description generation | batch_6a00b7faee908190906aae5233ea3122 |
completed | May 10, 2026, 4:53 p.m. |
Created at: April 29, 2026, 9:19 p.m.