Triple
T6070698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | gold rhinoceros |
E135271
|
entity |
| Predicate | importanceInPublicMemory |
P37289
|
FINISHED |
| Object | icon of African precolonial achievement |
—
|
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: icon of African precolonial achievement | Statement: [gold rhinoceros, importanceInPublicMemory, icon of African precolonial achievement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: importanceInPublicMemory Context triple: [gold rhinoceros, importanceInPublicMemory, icon of African precolonial achievement]
-
A.
historicalNotability
chosen
Indicates that an entity is recognized as having significant importance, influence, or prominence in history.
-
B.
wasProminentIn
Indicates that an entity was notably active, influential, or widely recognized within a particular field, context, or time period.
-
C.
hasHistoricalSignificance
Indicates that something possesses notable importance or influence within a historical context or period.
-
D.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
E.
hasNamesakeNotability
Indicates that one entity is notable or recognized specifically because it shares the same name as 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_69c00879e8048190b690717d19c5bc03 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05742867481908e3f45c875807c73 |
completed | March 22, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69c049f21fe08190995df3c5c05fb8ea |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:10 p.m.