Triple
T394152
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suez Canal |
E8943
|
entity |
| Predicate | maximumShipBeam |
P12550
|
FINISHED |
| Object | about 77.5 m |
—
|
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 77.5 m | Statement: [Suez Canal, maximumShipBeam, about 77.5 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maximumShipBeam Context triple: [Suez Canal, maximumShipBeam, about 77.5 m]
-
A.
maximumVesselType
Indicates the highest or largest class, size, or category of vessel that is allowed, applicable, or associated in a given context.
-
B.
standardDisplacement
Indicates the typical or officially specified amount of displacement (such as volume, weight, or capacity) associated with an entity under standard conditions.
-
C.
hullType
Indicates the specific structural design or configuration of an object's hull, typically classifying how its outer body or shell is shaped or constructed.
-
D.
naveHeight
Indicates the vertical distance from the floor to the highest point of the nave space in a building.
-
E.
maximumBreadthOfTerritorialSea
Indicates the greatest legally defined width of a state's territorial sea measured from its baseline.
- F. None of above. chosen
Provenance (4 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec77a8a08190b6f96373aa8c1346 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96bd3848190a66ca14dfbd26da5 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea7d03a88190aab72e61d8673488 |
completed | Feb. 28, 2026, 1:15 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.