Triple
T10970747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amazigh New Year |
E259225
|
entity |
| Predicate | associatedYearCount |
P75923
|
FINISHED |
| Object | Amazigh year count starting in 950 BC |
—
|
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: Amazigh year count starting in 950 BC | Statement: [Amazigh New Year, associatedYearCount, Amazigh year count starting in 950 BC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedYearCount Context triple: [Amazigh New Year, associatedYearCount, Amazigh year count starting in 950 BC]
-
A.
relatedYear
Indicates a connection between an entity and a specific year that is relevant to its occurrence, validity, or significance.
-
B.
activeInYears
Indicates that an entity was active or operational during the specified years or year range.
-
C.
durationInYears
Indicates the length of time associated with something, measured in whole or fractional years.
-
D.
appliesInYears
Indicates that something (such as a rule, condition, or effect) is valid, relevant, or in force during specific years.
-
E.
hasAssociatedYear
chosen
Indicates that an entity is linked to a specific year that is relevant to it (e.g., creation, occurrence, or reference year).
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7719a27488190b0b723cd0aba40bd |
completed | April 9, 2026, 9:30 a.m. |
| PD | Predicate disambiguation | batch_69d72e8c27cc81908050590b7a04cafd |
completed | April 9, 2026, 4:43 a.m. |
Created at: April 8, 2026, 9:24 p.m.