Triple
T38330787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heroes Day (Kenya) |
E1037813
|
entity |
| Predicate | timePeriodHonored |
P123510
|
FINISHED |
| Object | pre-independence 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: pre-independence era | Statement: [Heroes Day (Kenya), timePeriodHonored, pre-independence era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodHonored Context triple: [Heroes Day (Kenya), timePeriodHonored, pre-independence era]
-
A.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
B.
timePeriodPreserved
Indicates that a specific time period or historical era is maintained, conserved, or kept intact in its original or intended state.
-
C.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
D.
timePeriodQualifier
Indicates how a time-related statement or value is further specified or constrained, such as by defining its scope, phase, or contextual condition within a broader time period.
-
E.
timePeriodAttributed
chosen
Indicates that a specific time period is assigned or associated with an entity as its relevant temporal context.
- 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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd864235b481908738dbb69556bc62 |
completed | May 8, 2026, 6:44 a.m. |
| PD | Predicate disambiguation | batch_69fd8373b6bc819091c554f29ee17fec |
completed | May 8, 2026, 6:32 a.m. |
Created at: May 3, 2026, 4:30 p.m.