Triple
T30689138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuttering Bill |
E781269
|
entity |
| Predicate | ageInPrimaryTimeline |
P94404
|
FINISHED |
| Object | child during 1958 events |
—
|
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 during 1958 events | Statement: [Stuttering Bill, ageInPrimaryTimeline, child during 1958 events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageInPrimaryTimeline Context triple: [Stuttering Bill, ageInPrimaryTimeline, child during 1958 events]
-
A.
ageDuringNarration
Indicates that an entity has a specified age at the time when the described narrative or event is taking place.
-
B.
ageInPrimaryWork
Indicates the age of an entity (typically a person or character) within the context of their primary work or main creative output.
-
C.
currentAge
Indicates the present age or number of years that an entity has lived or existed up to now.
-
D.
timeRelativeToBirth
Indicates the temporal position of an event or state relative to an entity’s birth (e.g., before, at, or after birth).
-
E.
ageDuringMainEvents
chosen
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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b7b03488190b1db5fde4c7dd6e5 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:33 p.m.