Triple
T2360041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zachariah Chandler |
E47249
|
entity |
| Predicate | wasActiveIn |
P7685
|
FINISHED |
| Object | 19th century |
—
|
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: 19th century | Statement: [Zachariah Chandler, wasActiveIn, 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasActiveIn Context triple: [Zachariah Chandler, wasActiveIn, 19th century]
-
A.
historicallyActiveIn
chosen
Indicates that an entity was active or engaged in significant activities within a particular place or context during a past historical period.
-
B.
wasIn
Indicates that an entity existed, occurred, or was located within a particular place or context during a specified time or situation.
-
C.
wasAmong
Indicates that an entity belonged to, was included in, or was part of a particular group, set, or collection.
-
D.
livedDuring
Indicates that the subject existed or was alive at some point within the time period or lifespan associated with the object.
-
E.
hasActivityIn
Indicates that an entity engages in or performs a particular activity within a specified context, location, or domain.
- 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_69a88a1a4a6081908645b0f2914521ab |
completed | March 4, 2026, 7:38 p.m. |
| NER | Named-entity recognition | batch_69abc722ac3c819091f4316a4a166a77 |
completed | March 7, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69abc599b92c819093d9e15d4437705d |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:55 p.m.