Triple
T26483968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | From Head to Toe |
E664768
|
entity |
| Predicate | learningDomain |
P126649
|
FINISHED |
| Object | early childhood development |
—
|
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: early childhood development | Statement: [From Head to Toe, learningDomain, early childhood development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: learningDomain Context triple: [From Head to Toe, learningDomain, early childhood development]
-
A.
trainingDomain
Indicates that an entity is associated with or operates within a particular field, area, or domain of training.
-
B.
learnedIn
Indicates that an entity acquired knowledge, skills, or information within a particular context, environment, or source.
-
C.
educationalField
chosen
Indicates the academic or disciplinary area in which an educational activity, program, or qualification is focused.
-
D.
learn
Indicates that an entity acquires knowledge, skills, or understanding from another entity, source, or experience.
-
E.
educationalHubFor
Indicates that one entity serves as a central place or resource for providing education, learning opportunities, or academic support to another entity.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612fd2bdc8190b5f8bcd31b57186f |
completed | May 2, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:29 a.m.