Triple
T12919230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guggenheim Abu Dhabi |
E309069
|
entity |
| Predicate | hasPlannedProgram |
P6928
|
FINISHED |
| Object | education programs |
—
|
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: education programs | Statement: [Guggenheim Abu Dhabi, hasPlannedProgram, education programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlannedProgram Context triple: [Guggenheim Abu Dhabi, hasPlannedProgram, education programs]
-
A.
hasProgramme
chosen
Indicates that an entity is associated with or offers a particular programme (such as a course of study, plan, or structured set of activities).
-
B.
hasPlan
Indicates that an entity possesses or is associated with a specific plan or course of action.
-
C.
hasGlobalProgramme
Indicates that an entity operates, participates in, or is associated with a programme that is implemented or recognized at a global or international level.
-
D.
hasPlanningStatus
Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
-
E.
hasWorkProgram
Indicates that an entity offers, participates in, or is associated with a specific work-related program or scheme.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d971e6d9fc8190b8a5244b26b5f78a |
completed | April 10, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69d96fa9b7708190a9e9fa30f59ff580 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:41 p.m.