Triple
T31755049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boomerang roller coaster model |
E810534
|
entity |
| Predicate | layoutFootprint |
P172181
|
FINISHED |
| Object | compact |
—
|
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: compact | Statement: [Boomerang roller coaster model, layoutFootprint, compact]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layoutFootprint Context triple: [Boomerang roller coaster model, layoutFootprint, compact]
-
A.
layoutShape
Indicates a spatial or structural arrangement relationship where one entity defines or influences the geometric shape or configuration of another.
-
B.
layoutSupport
Indicates that one entity provides or enables structural or spatial arrangement capabilities for another entity.
-
C.
occupiesFootprintOf
chosen
Indicates that one entity physically lies within, matches, or uses the spatial footprint or ground area defined by another entity.
-
D.
layoutDetail
Indicates the specific arrangement or configuration details of how elements are laid out in relation to each other.
-
E.
layoutUnit
Indicates a relationship where one entity serves as the unit of measurement or basic spatial division used to define or structure the layout of another entity.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab7bcad88190acb61c516f87eff0 |
completed | May 3, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69f6aa20a1588190a53533fc9764efb2 |
completed | May 3, 2026, 1:51 a.m. |
Created at: April 30, 2026, 11:29 p.m.