Triple
T2670600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ife bronze and terracotta sculpture |
E55736
|
entity |
| Predicate | foundAt |
P9687
|
FINISHED |
| Object | Ife archaeological sites |
—
|
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: Ife archaeological sites | Statement: [Ife bronze and terracotta sculpture, foundAt, Ife archaeological sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundAt Context triple: [Ife bronze and terracotta sculpture, foundAt, Ife archaeological sites]
-
A.
foundInVolume
Indicates that one entity is physically or logically contained within, or occurs in, a specific volume (such as a book volume, data volume, or bounded collection).
-
B.
containsFinding
Indicates that one entity includes, encompasses, or holds a particular finding as part of its content or results.
-
C.
foundInRegion
chosen
Indicates that something is located within, occurs in, or is associated with a specific geographic or spatial region.
-
D.
foundInChapter
Indicates that something (such as a concept, section, or element) is contained within or occurs in a specific chapter.
-
E.
finds
Indicates that one entity discovers, locates, or comes upon another entity, often as the result of a search or encounter.
- 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_69ab49e54de48190be708cd1cf8be073 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd98e7d00819088398206fc7db477 |
completed | March 7, 2026, 7:53 a.m. |
| PD | Predicate disambiguation | batch_69abd8190ad481908f3e14ac84d0940a |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:54 p.m.