Triple
T29328296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marine Power & Equipment Company |
E743711
|
entity |
| Predicate | builtVesselClass |
P51721
|
FINISHED |
| Object | Issaquah-class ferry |
—
|
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: Issaquah-class ferry | Statement: [Marine Power & Equipment Company, builtVesselClass, Issaquah-class ferry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtVesselClass Context triple: [Marine Power & Equipment Company, builtVesselClass, Issaquah-class ferry]
-
A.
shipClassDeveloped
Indicates that a particular ship class was developed or designed by a specified entity (such as a country, organization, or manufacturer).
-
B.
shipTypeProduced
chosen
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
C.
shipClass
Indicates the classification or type category to which a particular ship belongs.
-
D.
vesselDesignation
Indicates that a specific identifying designation (such as a name, number, or code) is assigned to a vessel.
-
E.
navalClassGeneration
Indicates that one naval class belongs to a particular generational sequence or iteration relative to another naval class.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6689782388190a36b98ec2d60d63f |
completed | May 2, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 1:28 p.m.