Triple
T355137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ann Putnam Jr. |
E7525
|
entity |
| Predicate | ageDuringEvent |
P2042
|
FINISHED |
| Object | about 12 years old during the Salem witch trials |
—
|
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: about 12 years old during the Salem witch trials | Statement: [Ann Putnam Jr., ageDuringEvent, about 12 years old during the Salem witch trials]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ageDuringEvent Context triple: [Ann Putnam Jr., ageDuringEvent, about 12 years old during the Salem witch trials]
-
A.
ageRange
Indicates the span of ages within which an entity or relationship is considered valid or applicable.
-
B.
hasAge
chosen
Indicates that an entity possesses a specific age value, typically expressed as a number of time units since its birth or creation.
-
C.
participatedInEvent
Indicates that an entity took part in or was actively involved in a specific event.
-
D.
livedDuring
Indicates that the subject existed or was alive at some point within the time period or lifespan associated with the object.
-
E.
occurredDuring
Indicates that one event or action took place within the temporal span of another event or time period.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb8312f4819084dc222e665fded3 |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9589e7c8190b2d3af8f858c96af |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.