Triple
T6445350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boer–Zulu conflicts |
E138327
|
entity |
| Predicate | hasEarliestEvents |
P64188
|
FINISHED |
| Object | 1830s |
—
|
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: 1830s | Statement: [Boer–Zulu conflicts, hasEarliestEvents, 1830s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEarliestEvents Context triple: [Boer–Zulu conflicts, hasEarliestEvents, 1830s]
-
A.
earliestDate
chosen
Indicates the earliest point in time at which an associated event, state, or relationship is considered to begin or be valid.
-
B.
hasPrecedingEvents
Indicates that one or more events occurred earlier in time or sequence relative to the referenced event.
-
C.
isEarliestAgeOf
Indicates that one value represents the minimum or first age at which a specified condition, event, or state occurs for an entity.
-
D.
youngestEvent
Indicates that the referenced event is the most recent or last-occurring event among a set of events.
-
E.
earliestState
Indicates that one state or condition occurs before all other related states in time, representing the earliest point in a sequence.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698d866c81909ef3e0a53833ff7d |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:46 p.m.