Triple
T20984911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Every Child Matters |
E516868
|
entity |
| Predicate | hasOutcomeArea |
P124779
|
FINISHED |
| Object | being healthy |
—
|
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: being healthy | Statement: [Every Child Matters, hasOutcomeArea, being healthy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutcomeArea Context triple: [Every Child Matters, hasOutcomeArea, being healthy]
-
A.
hasAwardedArea
Indicates that one entity has formally granted or designated a specific area or territory to another entity.
-
B.
hasImpactArea
chosen
Indicates that an entity affects, influences, or has consequences within a specific area, domain, or scope.
-
C.
hasOutcomeIndicator
Indicates that something is associated with a specific measure or indicator used to evaluate its outcome or results.
-
D.
hasAreaType
Indicates that an entity is associated with a specific kind or classification of area (e.g., urban, rural, coastal).
-
E.
hasFinalArea
Indicates that an entity is associated with a specific area value representing its final or resulting size after some process or transformation.
- 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_69e0b4ffac148190bbade9f0eceb660b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fbe218748190a987b9f922d9be1b |
completed | April 21, 2026, 4:24 a.m. |
| PD | Predicate disambiguation | batch_69e5dbec80708190a49bccab7ff97e7b |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:48 p.m.