Triple
T5307195
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Production Central |
E120130
|
entity |
| Predicate | roleInPark |
P37484
|
FINISHED |
| Object | central hub for attractions |
—
|
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: central hub for attractions | Statement: [Production Central, roleInPark, central hub for attractions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInPark Context triple: [Production Central, roleInPark, central hub for attractions]
-
A.
roleInAttraction
Indicates the specific function or position an entity holds within the context of a particular attraction or point of interest.
-
B.
primaryRoleInPark
chosen
Indicates the main function or responsibility an entity has within a particular park.
-
C.
partOfAttractionType
Indicates that one attraction type is a component or subset of a broader, more general attraction type.
-
D.
isAttractionFor
Indicates that one entity serves as an attraction or point of interest specifically intended for another entity (such as a person, group, or audience).
-
E.
themeParkConnection
Indicates a relationship where two or more entities are connected through a theme park, such as by location, operation, partnership, or shared attractions.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.