Triple
T32134506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakela Ubhauli |
E820733
|
entity |
| Predicate | ageParticipation |
P108861
|
FINISHED |
| Object | all age groups |
—
|
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: all age groups | Statement: [Sakela Ubhauli, ageParticipation, all age groups]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageParticipation Context triple: [Sakela Ubhauli, ageParticipation, all age groups]
-
A.
hasAgeParticipation
Indicates a relationship where an entity’s participation or involvement is characterized or constrained by a specific age or age range.
-
B.
ageGroupInvolved
chosen
Indicates that a particular age group participates in, is affected by, or is otherwise involved in the specified event or relationship.
-
C.
ageInPlay
Indicates that an entity’s age is relevant or applicable within the context of a particular play, game, or interactive scenario.
-
D.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
E.
ageType
Indicates the specific categorization or classification of an age value (e.g., actual, estimated, range-based) associated with an 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:30 a.m.