Triple
T35906188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seaspan Shipyards |
E1038477
|
entity |
| Predicate | majorProgram |
P12153
|
FINISHED |
| Object | National Shipbuilding Strategy |
—
|
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: National Shipbuilding Strategy | Statement: [Seaspan Shipyards, majorProgram, National Shipbuilding Strategy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorProgram Context triple: [Seaspan Shipyards, majorProgram, National Shipbuilding Strategy]
-
A.
hasMajorProgram
Indicates that an educational institution offers a specific field of study as a primary academic program.
-
B.
majorProject
chosen
Indicates that an entity is a primary, large-scale, or most significant project associated with another entity.
-
C.
majorPass
Indicates that an entity successfully completes or passes a significant or primary stage, requirement, or examination in relation to another entity or process.
-
D.
major
Indicates that one entity is the primary field of academic specialization or main area of study for another entity.
-
E.
majorFor
Indicates that an academic program, field of study, or specialization is the primary major associated with a particular student or degree.
- 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_69f76e2259608190bf6788a132e0d139 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ffa15d53208190ab8574d6c7913e18 |
completed | May 9, 2026, 9:04 p.m. |
| PD | Predicate disambiguation | batch_69ff9eee681c81909434e79c627cb528 |
completed | May 9, 2026, 8:54 p.m. |
Created at: May 3, 2026, 4:07 p.m.