Triple
T29390814
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Regular Category (World Robot Olympiad) |
E745364
|
entity |
| Predicate | hasAgeGrouping |
P100475
|
FINISHED |
| Object | age-based divisions |
—
|
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: age-based divisions | Statement: [Regular Category (World Robot Olympiad), hasAgeGrouping, age-based divisions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgeGrouping Context triple: [Regular Category (World Robot Olympiad), hasAgeGrouping, age-based divisions]
-
A.
ageGroupIndicated
Indicates that a specific age range or category is identified or assigned to an entity.
-
B.
ageGroupSystem
chosen
Indicates a classification relationship where entities are grouped according to a defined system of age-based categories.
-
C.
hasApproximateAgeRange
Indicates that one entity is associated with another entity representing an estimated or non-exact span of ages.
-
D.
ageGroup
Indicates the categorical age range or bracket to which an entity belongs.
-
E.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of 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_69f0a79dfabc81908755382ee47791e2 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f669d648488190b7d3060432eb0eeb |
completed | May 2, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69f660f4f7a88190b93c60d76b86c912 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 2:42 p.m.