Triple
T17298308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peninsular and Oriental Steam Navigation Company |
E419968
|
entity |
| Predicate | operatedTypeOfVessel |
P11978
|
FINISHED |
| Object | steamships |
—
|
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: steamships | Statement: [Peninsular and Oriental Steam Navigation Company, operatedTypeOfVessel, steamships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatedTypeOfVessel Context triple: [Peninsular and Oriental Steam Navigation Company, operatedTypeOfVessel, steamships]
-
A.
operatesVessel
Indicates that an agent is responsible for controlling, managing, or running the operation of a vessel.
-
B.
hasVesselType
chosen
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
-
C.
IMOCategory
Indicates the classification of an entity according to the International Mathematical Olympiad (IMO) category it belongs to.
-
D.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
E.
typeOfMediumship
Indicates a relationship where one entity specifies the particular form or method of mediumship practiced or involved in relation to another entity.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438f82788819088ea796850552297 |
completed | April 19, 2026, 2:07 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
Created at: April 10, 2026, 5:41 a.m.