Triple
T5914973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children’s Museum |
E131555
|
entity |
| Predicate | suitableForAgeGroup |
P3005
|
FINISHED |
| Object | children aged 3–12 |
—
|
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 aged 3–12 | Statement: [Children’s Museum, suitableForAgeGroup, children aged 3–12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suitableForAgeGroup Context triple: [Children’s Museum, suitableForAgeGroup, children aged 3–12]
-
A.
isFamilyFriendly
Indicates that something is suitable for all ages and does not contain content inappropriate for children or sensitive audiences.
-
B.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
portraysAgeGroup
Indicates that one entity depicts or represents another entity as belonging to a particular age group.
-
D.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
-
E.
servesAgeRange
chosen
Indicates that a service, product, or offering is intended for or applicable to entities within a specified age range.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:59 p.m.