Triple
T20764038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ernst Thälmann Pioneer Organisation |
E511047
|
entity |
| Predicate | ageRangeOfThälmannPioneers |
P2736
|
FINISHED |
| Object | approximately 10–14 |
—
|
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: approximately 10–14 | Statement: [Ernst Thälmann Pioneer Organisation, ageRangeOfThälmannPioneers, approximately 10–14]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRangeOfThälmannPioneers Context triple: [Ernst Thälmann Pioneer Organisation, ageRangeOfThälmannPioneers, approximately 10–14]
-
A.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
typicalAgeRangeLower
Indicates the minimum age value that typically marks the lower bound of an expected or common age range for something.
-
C.
typicalAgeRangeOfPlayers
Indicates the usual age range of people who typically play or participate in something.
-
D.
hasProtagonistAgeRange
Indicates that a work’s main character falls within a specified age range.
-
E.
typicalAge
Indicates the usual or characteristic age associated with an entity, event, or condition.
- 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_69e0b4ca01148190ac018e57e0cab46f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c24b18b8819082e61104be6f83a3 |
completed | April 21, 2026, 12:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c0509608819080cdbf47fcddfe36 |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 12:35 p.m.