Triple
T18497461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dundee Shipbuilders Company |
E451984
|
entity |
| Predicate | usedForShips |
P131899
|
FINISHED |
| Object | commercial vessels |
—
|
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: commercial vessels | Statement: [Dundee Shipbuilders Company, usedForShips, commercial vessels]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedForShips Context triple: [Dundee Shipbuilders Company, usedForShips, commercial vessels]
-
A.
shipsUsedAs
Indicates that certain ships are employed or repurposed to serve in a specified role, function, or capacity.
-
B.
shipUsed
Indicates that a particular ship was employed or utilized in carrying out an event, activity, or operation.
-
C.
usedOnShipClass
Indicates that something (such as equipment, technology, or a system) is employed or installed on a particular class of ship.
-
D.
appliesToShips
Indicates that the specified condition, rule, or attribute is relevant to or affects ships.
-
E.
warshipTypeUsed
Indicates that a particular type or class of warship is employed or utilized in a given context, event, or operation.
- F. None of above. chosen
Provenance (4 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c15dec8190941e7c7a4cdebb66 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
| PDg | Predicate description generation | batch_69e46d2b93bc8190a6070018d7046547 |
completed | April 19, 2026, 5:50 a.m. |
Created at: April 10, 2026, 11:36 a.m.