Triple
T27885610
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reversi |
E705213
|
entity |
| Predicate | hasAgeRecommendation |
P102642
|
FINISHED |
| Object | suitable for children and adults |
—
|
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: suitable for children and adults | Statement: [Reversi, hasAgeRecommendation, suitable for children and adults]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAgeRecommendation Context triple: [Reversi, hasAgeRecommendation, suitable for children and adults]
-
A.
hasAgeGuidelines
Indicates that there are specified age-related rules or recommendations governing how something should be accessed, used, or engaged with.
-
B.
hasAgeClassification
Indicates that an entity is associated with a specific age-based category or grouping.
-
C.
ageRatingContext
Indicates the contextual basis or circumstances (such as region, system, or criteria) under which an age rating is assigned or interpreted.
-
D.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
E.
intendedForAgeGroup
chosen
Indicates that something is designed, suitable, or targeted for use by a specific age group.
- 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_69ef96b39c448190a9b3aa6672a5168f |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 6:32 p.m.