Triple
T33439105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luristan bronzes |
E856310
|
entity |
| Predicate | typicalFindSpot |
P105549
|
FINISHED |
| Object | grave 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: grave sites | Statement: [Luristan bronzes, typicalFindSpot, grave sites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFindSpot Context triple: [Luristan bronzes, typicalFindSpot, grave sites]
-
A.
originalFindspot
Indicates the location where an object or artifact was first discovered or found in situ.
-
B.
typicalLocationInTomb
chosen
Indicates the usual or most common place where something is found or situated within a tomb.
-
C.
findspotsInclude
Indicates that the specified findspots contain or encompass the referenced items or entities within them.
-
D.
cultLocation
Indicates that a cult or religious group is based in, practices in, or is primarily associated with a particular location.
-
E.
fossilsFoundAt
Indicates that fossil remains of an organism or taxon have been discovered at a particular location or site.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f505c88190ac0879ab422c3054 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:37 a.m.