Triple
T31310769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African Romance |
E798455
|
entity |
| Predicate | wentExtinctBy |
P11825
|
FINISHED |
| Object | around 11th century |
—
|
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: around 11th century | Statement: [African Romance, wentExtinctBy, around 11th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wentExtinctBy Context triple: [African Romance, wentExtinctBy, around 11th century]
-
A.
hasExtinction
Indicates that an entity has undergone, is subject to, or is associated with an extinction event or state of no longer existing.
-
B.
extinct
chosen
Indicates that the referenced entity no longer exists as a living or active member of its former kind or category.
-
C.
extinctUpon
Indicates that one entity ceases to exist or becomes extinct as a direct consequence of, or at the point of, another specified event or condition.
-
D.
titleExtinct
Indicates that a formal title or rank is no longer in existence or officially recognized.
-
E.
thoughtExtinct
Indicates that something was previously believed to no longer exist or to have died out, but is now recognized or suggested to still exist.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d1bf8cc8190a78dfa5ab00daf3a |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 29, 2026, 9:15 p.m.