Triple
T15833401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qiddiya entertainment city |
E383925
|
entity |
| Predicate | hasPlannedFacilityType |
P348
|
FINISHED |
| Object | theme park |
—
|
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: theme park | Statement: [Qiddiya entertainment city, hasPlannedFacilityType, theme park]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedFacilityType Context triple: [Qiddiya entertainment city, hasPlannedFacilityType, theme park]
-
A.
plannedFacility
chosen
Indicates that a facility is intended or scheduled to be built, established, or implemented in the future but does not yet exist or operate.
-
B.
hasFacilityType
Indicates that an entity possesses or is associated with a specific type or category of facility.
-
C.
hasPlanningType
Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
-
D.
designedFacilityType
Indicates the type or category of facility that something (such as a plan, system, or component) is specifically designed for.
-
E.
hasPlannedCapacity
Indicates that an entity is associated with a specified capacity level that is planned or intended for future use rather than currently realized.
- 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_69d86da34c888190976e06c4019d415a |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e11e6670d48190a456581dd951f168 |
completed | April 16, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69e005418f588190824d91ff7974dada |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.