Triple
T10624602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | H3RC |
E250289
|
entity |
| Predicate | associatedWithGrossTonnage |
P19645
|
FINISHED |
| Object | 219079 GT |
—
|
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: 219079 GT | Statement: [H3RC, associatedWithGrossTonnage, 219079 GT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithGrossTonnage Context triple: [H3RC, associatedWithGrossTonnage, 219079 GT]
-
A.
grossTonnage
chosen
Indicates the total internal volume or carrying capacity of a vessel, measured in gross tons, as defined by maritime tonnage rules.
-
B.
maxVesselTonnage
Indicates the maximum tonnage capacity that a vessel is allowed or designed to carry.
-
C.
tonnageClass
Indicates a classification relationship where an entity is assigned to a category based on its tonnage (weight or carrying capacity range).
-
D.
deadweightTonnage
Indicates the total carrying capacity of a vessel, measured as the maximum weight of cargo, fuel, passengers, provisions, and other loads it can safely transport.
-
E.
tonnage
Indicates the relationship between an object and the measure of its weight or cargo capacity, typically expressed in tons.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6df7fe9fc81908b3b8d1dc06a829c |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7fae088190973f70c69738af49 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 8:53 p.m.