Triple
T2874873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wamsutta |
E56851
|
entity |
| Predicate | approximateDeathTime |
P28122
|
FINISHED |
| Object | early 1660s |
—
|
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: early 1660s | Statement: [Wamsutta, approximateDeathTime, early 1660s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateDeathTime Context triple: [Wamsutta, approximateDeathTime, early 1660s]
-
A.
timeOfDeath
Indicates the specific time at which an entity (typically a person or organism) died.
-
B.
approximateAgeAtDeath
Indicates the estimated age a person or entity was when they died, typically used when the exact age is unknown.
-
C.
deathApprox
chosen
Indicates that an entity’s death occurred at an approximate, rather than exact, time or date.
-
D.
killedAt
Indicates that a killing event occurred at a specific location or time associated with the entities involved.
-
E.
killedApproximate
Indicates that one entity caused the death of another, but the information about this killing is uncertain, estimated, or not known with exact precision.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe004a64481908f1897d9054a7368 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.