Triple
T25792737
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kolb family |
E649592
|
entity |
| Predicate | locatedInTimeDuringKeyEvents |
P142986
|
FINISHED |
| Object | American Civil War era |
—
|
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: American Civil War era | Statement: [Kolb family, locatedInTimeDuringKeyEvents, American Civil War era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInTimeDuringKeyEvents Context triple: [Kolb family, locatedInTimeDuringKeyEvents, American Civil War era]
-
A.
locatedInTimeBefore
Indicates that one temporal event or interval occurs entirely before another in time.
-
B.
hasNearbyHistoricalEvent
Indicates that a given entity is located close to the site where a specific historical event occurred.
-
C.
notableEventTime
Indicates the specific time at which a notable or significant event occurred.
-
D.
chronologicallyInvolvedIn
chosen
Indicates that an entity participates in or is associated with an event, process, or activity during a specific time period in a chronological sequence.
-
E.
hasHistoricalEvent
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
- 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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 22, 2026, 6 a.m.