Triple
T8716251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panamax |
E206900
|
entity |
| Predicate | hasMaxDraftTropicalFreshWater |
P34007
|
FINISHED |
| Object | about 12.04 metres |
—
|
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 12.04 metres | Statement: [Panamax, hasMaxDraftTropicalFreshWater, about 12.04 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxDraftTropicalFreshWater Context triple: [Panamax, hasMaxDraftTropicalFreshWater, about 12.04 metres]
-
A.
maximumDraft
Indicates that there is an upper limit on the number of drafts that can be created, stored, or associated with a given entity or process.
-
B.
maximumWaterDepth
Indicates the greatest depth of water present or allowed in a given context, such as a location, container, or body of water.
-
C.
hasMaxDraftApprox
chosen
Indicates that one entity has, as an upper bound, an approximate maximum value or level for a draft-related quantity associated with another entity.
-
D.
receivesFreshwaterFrom
Indicates that one entity is supplied with or obtains freshwater from another entity as its source.
-
E.
lakeMaximumDepth
Indicates the greatest recorded vertical distance from the lake’s surface to its deepest point.
- 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.