Triple
T25785527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holland Torpedo Boat Company |
E649407
|
entity |
| Predicate | usedDesignsBy |
P80817
|
FINISHED |
| Object | John Philip Holland |
—
|
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: John Philip Holland | Statement: [Holland Torpedo Boat Company, usedDesignsBy, John Philip Holland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDesignsBy Context triple: [Holland Torpedo Boat Company, usedDesignsBy, John Philip Holland]
-
A.
designsBy
chosen
Indicates that one entity is the creator or designer responsible for the conception or design of another entity.
-
B.
designsFor
Indicates that one entity creates or plans something specifically intended to serve, suit, or be used by another entity.
-
C.
designUse
Indicates that one entity is used as a design basis, purpose, or intended functional use for another entity.
-
D.
usedDomesticDesigns
Indicates that one entity employed or incorporated designs originating from its own country or local context in relation to another entity or activity.
-
E.
usedDesignDevice
Indicates that one entity employed or operated a particular design-related device or tool.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fefa2c908190939ca0f6f68420ad |
completed | May 2, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 22, 2026, 5:54 a.m.