Triple
T26816521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dragon Wind |
E675133
|
entity |
| Predicate | locatedAtThemeParkResort |
P78442
|
FINISHED |
| Object | Hong Kong Disneyland Resort |
—
|
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: Hong Kong Disneyland Resort | Statement: [Dragon Wind, locatedAtThemeParkResort, Hong Kong Disneyland Resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedAtThemeParkResort Context triple: [Dragon Wind, locatedAtThemeParkResort, Hong Kong Disneyland Resort]
-
A.
locatedInThemeParkType
Indicates that an entity is situated within or belongs to a specific type or category of theme park.
-
B.
locatedInAttractionScene
Indicates that one entity is situated within or is part of the setting or scene of an attraction.
-
C.
themeParkAttractionLocation
Indicates the specific place or area within a theme park where a particular attraction is situated.
-
D.
countryParkLocatedOn
Indicates that a country park is situated on or within the area of a specified geographic feature or land unit.
-
E.
themeParkPresence
chosen
Indicates that an entity is present at, located in, or associated with a theme park in the context of a given event or situation.
- 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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fe08d2b2e48190ac7be6d62d4a44a3 |
completed | May 8, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69fe06cd3af08190ae25de0dc0cdd573 |
completed | May 8, 2026, 3:52 p.m. |
Created at: April 27, 2026, 4:52 a.m.