Triple
T8716255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panamax |
E206900
|
entity |
| Predicate | hasMaxDisplacement |
P84064
|
FINISHED |
| Object | about 65,000 deadweight tons |
—
|
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 65,000 deadweight tons | Statement: [Panamax, hasMaxDisplacement, about 65,000 deadweight tons]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxDisplacement Context triple: [Panamax, hasMaxDisplacement, about 65,000 deadweight tons]
-
A.
maximumHorizontalDisplacement
Indicates the greatest distance an entity can or does move horizontally from a reference point or along a horizontal axis.
-
B.
displacementRange
Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
-
C.
hasMaximumValue
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
-
D.
hasMaximumThickness
Indicates that an entity possesses a specified upper limit on its thickness.
-
E.
displacementRate
Indicates the rate at which an entity’s position changes over time relative to a reference point or frame.
- 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_69ca83572d4881909bef3be2b578d539 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5cd9c2a08190a65ab0ce573153d2 |
completed | March 31, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69cc456e806c819087e7d66ee737f242 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc46c40c54819093d174a4203f9515 |
completed | March 31, 2026, 10:12 p.m. |
Created at: March 30, 2026, 6:35 p.m.