Triple
T13800050
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lisebergbanan |
E331614
|
entity |
| Predicate | maxHeightRestriction |
P8078
|
FINISHED |
| Object | 195 cm |
—
|
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: 195 cm | Statement: [Lisebergbanan, maxHeightRestriction, 195 cm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxHeightRestriction Context triple: [Lisebergbanan, maxHeightRestriction, 195 cm]
-
A.
heightRestriction
chosen
Indicates that there is a limit or constraint on how tall an entity is allowed or required to be in a given context.
-
B.
heightRestrictionWithCompanion
Indicates that there is a height-based restriction which may be satisfied or modified when the person is accompanied by a qualifying companion.
-
C.
maximumCeiling
Indicates the highest allowable or achievable limit or value that something cannot exceed.
-
D.
dimensionRestriction
Indicates a constraint or limit imposed on the size, extent, or number of dimensions associated with an entity or relationship.
-
E.
hasMaximumStructureHeightRegulation
Indicates that there is a regulatory limit specifying the maximum allowable height for a structure.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de025ce9148190b23370f6a522ff7a |
completed | April 14, 2026, 9:01 a.m. |
| PD | Predicate disambiguation | batch_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.