Triple
T480742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nollywood |
E9159
|
entity |
| Predicate | notableFormat |
P14840
|
FINISHED |
| Object | video film era of the 1990s |
—
|
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: video film era of the 1990s | Statement: [Nollywood, notableFormat, video film era of the 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFormat Context triple: [Nollywood, notableFormat, video film era of the 1990s]
-
A.
notableText
Indicates that a particular piece of text is especially significant, prominent, or worthy of attention in relation to the associated entity or context.
-
B.
notableEdition
Indicates that a particular edition or version of a work is especially significant or noteworthy in relation to that work.
-
C.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
D.
notableRendering
Indicates that one entity is a significant or well-known visual or artistic depiction of another entity.
-
E.
notableStandard
Indicates that one entity is a widely recognized or influential standard that the other entity is associated with or exemplifies.
- F. None of above. chosen
Provenance (4 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_69a2e7ff81708190b0507a24a997232c |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2f058ebe48190aaa0a829b21f75fa |
completed | Feb. 28, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69a2edf321288190b5d560f75782c2cb |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2ef4030608190b39852b347a505ca |
completed | Feb. 28, 2026, 1:36 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.