Triple
T8716249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panamax |
E206900
|
entity |
| Predicate | hasMaxLengthOverall |
P56985
|
FINISHED |
| Object | about 294.13 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 294.13 metres | Statement: [Panamax, hasMaxLengthOverall, about 294.13 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxLengthOverall Context triple: [Panamax, hasMaxLengthOverall, about 294.13 metres]
-
A.
hasMaxLengthApprox
Indicates that something has a maximum length that is approximately equal to a specified value, allowing for some tolerance or imprecision.
-
B.
hasMaximumLength
chosen
Indicates that there is an upper limit on the length or size of something, beyond which it cannot extend.
-
C.
hasCategoryLengthRestriction
Indicates that there is a constraint on the allowable length of a category, such as its name, identifier, or structural size.
-
D.
hasMinimumLength
Indicates that the length of an entity (such as a sequence, string, or collection) is greater than or equal to a specified minimum value.
-
E.
hasLineLength
Indicates that one entity has, is characterized by, or is associated with a specific line length value.
- 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.