Triple
T34465873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ark Children’s Cultural Centre |
E884765
|
entity |
| Predicate | programmesDesignedFor |
P101502
|
FINISHED |
| Object | children |
—
|
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: children | Statement: [Ark Children’s Cultural Centre, programmesDesignedFor, children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmesDesignedFor Context triple: [Ark Children’s Cultural Centre, programmesDesignedFor, children]
-
A.
targetAudienceOfPrograms
chosen
Indicates that a particular group or entity is the intended audience or recipient of certain programs.
-
B.
developedForProgram
Indicates that something was created, designed, or produced specifically to be used in or support a particular program.
-
C.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
D.
programmedPurpose
Indicates that an entity has been intentionally designed or configured to fulfill a specific function, goal, or behavior.
-
E.
supportsProgrammesOf
Indicates that one entity provides assistance, resources, or endorsement to help another entity’s programmes operate or succeed.
- 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_69f349c73a94819094dfcf50d00620b8 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7675b12848190a3569cfda29c5b0e |
completed | May 3, 2026, 3:18 p.m. |
| PD | Predicate disambiguation | batch_69f762f4b59481909f70074f11825bfb |
completed | May 3, 2026, 3 p.m. |
Created at: May 1, 2026, 2:01 a.m.