Triple
T31342583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girgam |
E799347
|
entity |
| Predicate | isWrittenSourceFor |
P83832
|
FINISHED |
| Object | history of Kanem Empire |
—
|
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: history of Kanem Empire | Statement: [Girgam, isWrittenSourceFor, history of Kanem Empire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isWrittenSourceFor Context triple: [Girgam, isWrittenSourceFor, history of Kanem Empire]
-
A.
hasWriterSource
Indicates that the writer of one entity is derived from, based on, or sourced from another entity.
-
B.
isWrittenAs
Indicates that one entity is represented or expressed in written form as another entity (such as a specific spelling, notation, or symbol).
-
C.
isOfficialSourceFor
chosen
Indicates that one entity is recognized as an authoritative or formally sanctioned provider of information or content about another entity.
-
D.
isWritten
Indicates that a text, document, or content has been created or recorded in written form by an agent.
-
E.
containsSourceOf
Indicates that one entity includes, holds, or encompasses the origin or cause of another entity.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f15d4f8819098892ed7905af38c |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:17 p.m.