Triple
T7249548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ziza |
E156560
|
entity |
| Predicate | hasHistoricalCertainty |
P33842
|
FINISHED |
| Object | uncertain |
—
|
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: uncertain | Statement: [Ziza, hasHistoricalCertainty, uncertain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHistoricalCertainty Context triple: [Ziza, hasHistoricalCertainty, uncertain]
-
A.
hasUncertainHistoricBasis
chosen
Indicates that the historical foundation or authenticity of the related fact, event, or relationship is doubtful, disputed, or not firmly established.
-
B.
hasCertainty
Indicates that a statement, belief, or relationship is associated with a specific level or degree of confidence or surety.
-
C.
historicalExistence
Indicates that an entity actually existed at some point in real-world history, as opposed to being fictional, hypothetical, or mythological.
-
D.
hasHistoricalContext
Indicates that something is related to, influenced by, or best understood in light of specific past events, conditions, or time periods.
-
E.
hasHistoricalEntity
Indicates a relationship where one entity includes, references, or is associated with another entity that existed or is defined in a past historical 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_69c68827b5e481908dc05e145b2c92d4 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea77a3588190accf31860170f052 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.