Triple
T28636379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | youth creativity palace |
E724796
|
entity |
| Predicate | typicalParticipantsAgeRange |
P133912
|
FINISHED |
| Object | 6-18 years |
—
|
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: 6-18 years | Statement: [youth creativity palace, typicalParticipantsAgeRange, 6-18 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalParticipantsAgeRange Context triple: [youth creativity palace, typicalParticipantsAgeRange, 6-18 years]
-
A.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
typicalAgeRangeOfPlayers
chosen
Indicates the usual age range of people who typically play or participate in something.
-
C.
typicalAgeRangeLower
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
-
D.
typicalEligibilityAge
Indicates the usual or standard age at which an entity qualifies for or becomes eligible for a particular status, benefit, or activity.
-
E.
typicalGroupSizeRange
Indicates the usual minimum and maximum number of individuals that typically occur together in a group for the given 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_69f01d8328c48190bc0e5f9b9b848582 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a00d15f7b788190a3bf440be7837192 |
completed | May 10, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_6a00d0f8ef548190b1c15b06164eec4a |
completed | May 10, 2026, 6:39 p.m. |
Created at: April 28, 2026, 4:40 a.m.