Triple
T11995853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Seaver |
E285527
|
entity |
| Predicate | ageRangeDuringSeries |
P2736
|
FINISHED |
| Object | child to early teenager |
—
|
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: child to early teenager | Statement: [Ben Seaver, ageRangeDuringSeries, child to early teenager]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageRangeDuringSeries Context triple: [Ben Seaver, ageRangeDuringSeries, child to early teenager]
-
A.
ageInSeries
Indicates the age of an entity as it appears or is depicted within a specific series or installment of a work.
-
B.
ageRange
chosen
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
C.
ageDuringNarration
Indicates that an entity has a specified age at the time when the described narrative or event is taking place.
-
D.
portrayedByCharacterAgeApprox
Indicates that an entity is portrayed by a character whose age is approximately a specified value or age range.
-
E.
ageDuringMainEvents
Indicates the age an entity has at the time when the main events of a referenced context or narrative occur.
- 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_69d6ab44a77c8190a652f4b27164e4ef |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903b211688190bfe6dd15c3f96d2f |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.