Triple
T34159215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ever Ace |
E876226
|
entity |
| Predicate | containerCapacityTEU |
P18218
|
FINISHED |
| Object | approximately 23992 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: approximately 23992 TEU | Statement: [Ever Ace, containerCapacityTEU, approximately 23992 TEU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containerCapacityTEU Context triple: [Ever Ace, containerCapacityTEU, approximately 23992 TEU]
-
A.
maxVesselTonnage
Indicates the maximum tonnage capacity that a vessel is allowed or designed to carry.
-
B.
designedCargoCapacity
chosen
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
C.
cargoHoldVolume
Indicates the total internal volume available within a cargo hold for storing goods or materials.
-
D.
transportCapacity
Indicates the maximum quantity of people, goods, or materials that can be transported by an entity or system within a given operation or time frame.
-
E.
slingLoadCapacity
Indicates the maximum weight or load that can be safely carried or supported using a sling.
- 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_69f349ac987481908a8e6053f665bc8b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a005b2e0a9c819081c6f7ccbef49ff8 |
completed | May 10, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_6a005a8bcde88190ace2bc0215e26430 |
completed | May 10, 2026, 10:14 a.m. |
Created at: May 1, 2026, 1:54 a.m.