Triple
T17260946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iguvium |
E419006
|
entity |
| Predicate | hasReligionEvidence |
P27867
|
FINISHED |
| Object | pre-Roman Italic religion |
—
|
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: pre-Roman Italic religion | Statement: [Iguvium, hasReligionEvidence, pre-Roman Italic religion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReligionEvidence Context triple: [Iguvium, hasReligionEvidence, pre-Roman Italic religion]
-
A.
hadViewOnReligion
Indicates that an entity held a particular perspective, belief, or stance regarding religion.
-
B.
hasReligiousSee
Indicates that one entity serves as the ecclesiastical or religious jurisdiction/seat (see) of another entity.
-
C.
hadMajorReligion
Indicates that a particular religion was the primary or dominant faith practiced within a given entity (such as a region, state, or population) during a specified period.
-
D.
bearerReligion
Indicates that a bearer (such as a person or entity) adheres to, practices, or is associated with a particular religion.
-
E.
hasAssociatedReligion
chosen
Indicates that an entity is connected with or linked to a particular religion.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e70b00c8190b0380be08afae18d |
completed | April 19, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.