Triple
T8636009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dogon |
E204523
|
entity |
| Predicate | SiguiFrequency |
P85
|
FINISHED |
| Object | about every 60 years |
—
|
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: about every 60 years | Statement: [Dogon, SiguiFrequency, about every 60 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SiguiFrequency Context triple: [Dogon, SiguiFrequency, about every 60 years]
-
A.
symbolForFrequency
Indicates that one entity serves as the symbolic representation or notation used to denote the frequency of another entity or phenomenon.
-
B.
frequency
chosen
Indicates how often an event, action, or relationship occurs within a given period or context.
-
C.
hasCarrierFrequency
Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
-
D.
usesFrequency
Indicates that one entity employs or operates another entity at a specified rate, interval, or number of occurrences over time.
-
E.
hasFrequencyNote
Indicates that something is associated with a specific note describing how often it occurs or is repeated.
- 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_69ca834b903c8190add96cc651e1a477 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc47944d1c819081f448f14d04bf9d |
completed | March 31, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69cc455d6d448190a2da2a319ac78c37 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:27 p.m.