Triple
T9485247
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maelstrom |
E228743
|
entity |
| Predicate | manufacturer |
P490
|
FINISHED |
| Object | Intamin |
E114327
|
NE 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: Intamin | Statement: [Maelstrom, manufacturer, Intamin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Intamin Context triple: [Maelstrom, manufacturer, Intamin]
-
A.
Intamin
chosen
Intamin is a Swiss-based company renowned worldwide for designing and manufacturing major amusement rides and roller coasters for theme parks.
-
B.
Tokyo Denki
Tokyo Denki was a Japanese electrical company that became a predecessor of the modern electronics conglomerate Toshiba.
-
C.
Tokyu Land Corporation
Tokyu Land Corporation is a major Japanese real estate developer and property management company within the Tokyu Group conglomerate.
-
D.
Kawada Industries
Kawada Industries is a Japanese engineering and construction company known for its work on major infrastructure projects, including prominent bridges and civil works.
-
E.
Obayashi Corporation
Obayashi Corporation is a major Japanese construction and engineering company known for its involvement in large-scale infrastructure and building projects worldwide.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69ca84730a5081908de282651019bf2f |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd804fb2b4819084c7f5a842dbe5a6 |
completed | April 1, 2026, 8:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d12d1326b8819084c6d9490b7a96dc |
completed | April 4, 2026, 3:24 p.m. |
Created at: March 30, 2026, 7:55 p.m.