Triple
T31445723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spirit of Norway |
E802181
|
entity |
| Predicate | followsAttraction |
P194814
|
FINISHED |
| Object | Maelstrom |
—
|
NE NERFINISHED |
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: Maelstrom | Statement: [Spirit of Norway, followsAttraction, Maelstrom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsAttraction Context triple: [Spirit of Norway, followsAttraction, Maelstrom]
-
A.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
-
B.
connectsToAttraction
Indicates a relationship where one entity provides a direct link, route, or access to an attraction.
-
C.
basedOnAttraction
Indicates that the relationship or action occurs or is formed due to some form of attraction between the involved entities.
-
D.
attractionBasedOn
Indicates a relationship where one entity is drawn to or interested in another specifically because of certain attributes, qualities, or characteristics that the latter possesses.
-
E.
ridesAttraction
Indicates that an entity participates in experiencing or using an attraction, such as going on a ride at a venue or amusement location.
- 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_69f348c5a6bc819092a557e95438976f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
| PDg | Predicate description generation | batch_69fd884b9d908190833de9500ff6d62a |
completed | May 8, 2026, 6:52 a.m. |
Created at: April 30, 2026, 9:09 p.m.