Triple
T26432369
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebron production platform |
E664543
|
entity |
| Predicate | topsidesWeight |
P160748
|
FINISHED |
| Object | approximately 65,000 tonnes |
—
|
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: approximately 65,000 tonnes | Statement: [Hebron production platform, topsidesWeight, approximately 65,000 tonnes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topsidesWeight Context triple: [Hebron production platform, topsidesWeight, approximately 65,000 tonnes]
-
A.
hullWeight_kg
Indicates the weight of an object's hull measured in kilograms.
-
B.
emptyWeight
Indicates the weight of an object or vehicle when it is empty, excluding any load, cargo, or passengers.
-
C.
trophyWeight
Indicates a relationship where a specific weight value is attributed to a trophy.
-
D.
hullWeight_lb
Indicates the weight of a hull measured in pounds.
-
E.
weightingCap
Indicates that there is an upper limit or cap on the weighting that can be assigned in a given context or calculation.
- 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_69ee883ad6a4819088f918e76122d690 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f611bebb8481909d7be89946db38d1 |
completed | May 2, 2026, 3:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
| PDg | Predicate description generation | batch_69f604120e848190b516c29b781d19cc |
completed | May 2, 2026, 2:02 p.m. |
Created at: April 26, 2026, 11:50 p.m.