Triple
T29767294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suezmax |
E753949
|
entity |
| Predicate | maximumLengthOverall |
P140284
|
FINISHED |
| Object | about 275 meters |
—
|
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: about 275 meters | Statement: [Suezmax, maximumLengthOverall, about 275 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumLengthOverall Context triple: [Suezmax, maximumLengthOverall, about 275 meters]
-
A.
totalLength_m
chosen
Indicates the overall measured length of something expressed in meters.
-
B.
maximumShellLength
Indicates the greatest recorded length of an organism’s shell within a given context or dataset.
-
C.
maximumSegmentLength
Indicates the greatest allowable or observed length of a segment within a given context or structure.
-
D.
maxLengthGirth
Indicates that there is a maximum allowable or observed girth (thickness or circumference) associated with the related entity or relationship.
-
E.
maxLengthGirthUnit
Indicates the unit of measurement used to express the maximum girth length of an entity.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: April 28, 2026, 8:39 p.m.