Triple
T8716256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panamax |
E206900
|
entity |
| Predicate | hasMaxTEUCapacity |
P1931
|
FINISHED |
| Object | about 4,500 to 5,000 TEU |
—
|
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 4,500 to 5,000 TEU | Statement: [Panamax, hasMaxTEUCapacity, about 4,500 to 5,000 TEU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxTEUCapacity Context triple: [Panamax, hasMaxTEUCapacity, about 4,500 to 5,000 TEU]
-
A.
maximumTonnageLimitedBy
Indicates that the maximum allowable tonnage of one entity is constrained or capped by the capacity or limit specified by another entity.
-
B.
hasCraneCapacity
Indicates that an entity possesses a crane with a specified lifting capacity or load-handling capability.
-
C.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
D.
typicalCapacity
chosen
Indicates the usual or standard amount, volume, or capability that something is designed or expected to hold, handle, or perform under normal conditions.
-
E.
weightLimitInKilograms
Indicates the maximum allowable weight for something, expressed in kilograms.
- 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_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. |
Created at: March 30, 2026, 6:35 p.m.