Triple
T776063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS Jeremiah O’Brien |
E16388
|
entity |
| Predicate | grossTonnage |
P19645
|
FINISHED |
| Object | 7176 GRT |
—
|
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: 7176 GRT | Statement: [SS Jeremiah O’Brien, grossTonnage, 7176 GRT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: grossTonnage Context triple: [SS Jeremiah O’Brien, grossTonnage, 7176 GRT]
-
A.
cargoHoldVolume
Indicates the total internal volume available within a cargo hold for storing goods or materials.
-
B.
standardDisplacement
Indicates the typical or officially specified amount of displacement (such as volume, weight, or capacity) associated with an entity under standard conditions.
-
C.
announcedGrossVehicleWeightRating
Indicates that an entity has a specified gross vehicle weight rating that has been formally announced or declared.
-
D.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
E.
hullNumber
Indicates the unique identifying number assigned to the hull of a ship or vessel.
- 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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a74da7648190adfad56717d564df |
completed | March 1, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69a4a50a443481909ae3662764ee69a4 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a74c81bc81909f4ac9c1677b09c2 |
completed | March 1, 2026, 8:53 p.m. |
Created at: March 1, 2026, 7:37 p.m.