Triple
T33368606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Discovery |
E854423
|
entity |
| Predicate | replacedByAttraction |
P192717
|
FINISHED |
| Object | Nemo & Friends SeaRider |
—
|
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: Nemo & Friends SeaRider | Statement: [Port Discovery, replacedByAttraction, Nemo & Friends SeaRider]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByAttraction Context triple: [Port Discovery, replacedByAttraction, Nemo & Friends SeaRider]
-
A.
replacementAttraction
chosen
Indicates a relationship where one entity serves as a substitute or alternative attraction for another, typically when the original is unavailable or less preferred.
-
B.
relatedAttraction
Indicates that one attraction is associated with or connected to another attraction in some relevant way.
-
C.
basedOnAttraction
Indicates that the relationship or action occurs or is formed due to some form of attraction between the involved entities.
-
D.
previousAttraction
Indicates that one entity was formerly an attraction or point of interest associated with another entity in the past.
-
E.
connectsToAttraction
Indicates a relationship where one entity provides a direct link, route, or access to an attraction.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd6f9d600c8190acf495b7fc632e4b |
completed | May 8, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69fd6e98a2948190a9f78c415ad23b8c |
completed | May 8, 2026, 5:03 a.m. |
Created at: May 1, 2026, 1:35 a.m.