Triple
T14746759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tornado (Wet'n'Wild Gold Coast) |
E346490
|
entity |
| Predicate | mainElement |
P115615
|
FINISHED |
| Object | giant funnel |
—
|
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: giant funnel | Statement: [Tornado (Wet'n'Wild Gold Coast), mainElement, giant funnel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainElement Context triple: [Tornado (Wet'n'Wild Gold Coast), mainElement, giant funnel]
-
A.
primaryElement
Indicates that one element is the main or most important component within a set, structure, or context relative to other associated elements.
-
B.
primaryComponent
Indicates that one entity serves as the main or most important component within another entity or system.
-
C.
mainSingle
Indicates that an entity is the primary or sole main instance among a set of related entities.
-
D.
mainRite
Indicates that one ritual, ceremony, or rite is the primary or central rite associated with a given context, entity, or event.
-
E.
primaryView
Indicates that one view or representation is designated as the main or default perspective among multiple possible views of the same entity or content.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7d116e88190828b163b18d80f68 |
completed | April 14, 2026, 11:03 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:30 a.m.