Triple
T28686956
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union Iron Works |
E729160
|
entity |
| Predicate | builtVesselType |
P51721
|
FINISHED |
| Object | battleships |
—
|
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: battleships | Statement: [Union Iron Works, builtVesselType, battleships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: builtVesselType Context triple: [Union Iron Works, builtVesselType, battleships]
-
A.
shipTypeProduced
chosen
Indicates that a particular type of ship is produced, built, or manufactured by a given entity.
-
B.
craftType
Indicates the specific kind or category of craft or vessel associated with an entity.
-
C.
vesselTypeServedOn
Indicates the type of vessel on which an entity has served or performed duty.
-
D.
hullType
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
-
E.
hasVesselType
Indicates that an entity is associated with or classified by a specific type of vessel (e.g., ship, boat, or container).
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656823ae08190be9c9a15d7336169 |
completed | May 2, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:33 a.m.