Triple
T36146103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Liam Digby is mistaken for an adult |
E1045453
|
entity |
| Predicate | involvesAge |
P108861
|
FINISHED |
| Object | twelve-year-old boy |
—
|
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: twelve-year-old boy | Statement: [Liam Digby is mistaken for an adult, involvesAge, twelve-year-old boy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesAge Context triple: [Liam Digby is mistaken for an adult, involvesAge, twelve-year-old boy]
-
A.
ageGroupInvolved
chosen
Indicates that a particular age group participates in, is affected by, or is otherwise involved in the specified event or relationship.
-
B.
containsAge
Indicates that one entity includes or specifies the age value or age-related information of another entity.
-
C.
activeInAge
Indicates that an entity is active, relevant, or functioning during a specified age or age range.
-
D.
canAge
Indicates that one entity has the capability or property of undergoing aging over time.
-
E.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe5ec9028081909ae3d6fbe2f4cbbc |
completed | May 8, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69fe5e1d715881909fc516fafc707644 |
completed | May 8, 2026, 10:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.