Triple
T25758849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contrebia Belaisca |
E648678
|
entity |
| Predicate | hasFindspot |
P42654
|
FINISHED |
| Object | Botorrita bronze I |
—
|
NE NERFINISHED |
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: Botorrita bronze I | Statement: [Contrebia Belaisca, hasFindspot, Botorrita bronze I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFindspot Context triple: [Contrebia Belaisca, hasFindspot, Botorrita bronze I]
-
A.
originalFindspot
chosen
Indicates the location where an object or artifact was first discovered or found in situ.
-
B.
hasFindingSite
Indicates that a particular finding, observation, or abnormality is located in or associated with a specific anatomical site.
-
C.
fossilsFoundAt
Indicates that fossil remains of an organism or taxon have been discovered at a particular location or site.
-
D.
excavatedAt
Indicates that an excavation activity took place at a specific location or site.
-
E.
ashFoundIn
Indicates that ash is present within, or has been discovered in, a specified location or material.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 22, 2026, 4:43 a.m.