Triple
T18768863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Doraleh Container Terminal |
E458960
|
entity |
| Predicate | hasStorageCapacity |
P52985
|
FINISHED |
| Object | hundreds of thousands of 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: hundreds of thousands of TEU | Statement: [Doraleh Container Terminal, hasStorageCapacity, hundreds of thousands of TEU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStorageCapacity Context triple: [Doraleh Container Terminal, hasStorageCapacity, hundreds of thousands of TEU]
-
A.
hasStorage
Indicates that one entity provides or contains storage capacity or space for another entity or resource.
-
B.
storageCapacity
chosen
Indicates the maximum amount of data or material that a storage entity can hold.
-
C.
dataCapacity
Indicates the maximum amount of data that something can store, handle, or transmit.
-
D.
installedCapacity
Indicates the maximum output or production capability that has been set up or built for a system, facility, or equipment, typically measured under specified conditions.
-
E.
hasMemoryIn
Indicates that an entity possesses or stores memory, information, or experiences within a specified context, location, or medium.
- 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_69d8d395dba0819087568404508590cb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e58d867264819098ae35c9feab3bb4 |
completed | April 20, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69e48d0b7b708190877951b6e6cdcbc4 |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.