Triple
T8716250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panamax |
E206900
|
entity |
| Predicate | hasMaxBeam |
P7354
|
FINISHED |
| Object | about 32.31 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 32.31 metres | Statement: [Panamax, hasMaxBeam, about 32.31 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaxBeam Context triple: [Panamax, hasMaxBeam, about 32.31 metres]
-
A.
hasTypicalBeam
Indicates that an entity is associated with a characteristic or standard type of beam it commonly uses or possesses.
-
B.
hasBeamSpecies
Indicates a relationship where an object or structure possesses or is associated with a particular type or species of beam.
-
C.
hasBeamlines
Indicates that one entity possesses, contains, or is associated with one or more beamlines.
-
D.
canBeExceededIn
Indicates that one entity’s value, level, or extent is capable of being surpassed by that of another entity within a specified context.
-
E.
hasMaximumValue
chosen
Indicates that one value in a set is the greatest or highest possible according to a specified criterion.
- 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.