Triple
T22186340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fetiales |
E548305
|
entity |
| Predicate | paterPatratusRole |
P146753
|
FINISHED |
| Object | spokesman in fetial rituals |
—
|
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: spokesman in fetial rituals | Statement: [Fetiales, paterPatratusRole, spokesman in fetial rituals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paterPatratusRole Context triple: [Fetiales, paterPatratusRole, spokesman in fetial rituals]
-
A.
patriarch
Indicates a relationship where one entity serves as the male head or senior father-figure authority over a family, clan, or lineage of other entities.
-
B.
patriarchRank
Indicates the hierarchical rank or level of authority held by a patriarch within a structured lineage or leadership system.
-
C.
patriarchTitle
Indicates that one entity holds the role or title of patriarch in relation to another entity.
-
D.
fatherCultureRole
Indicates that one culture assumes a paternal or fatherly role in relation to another culture.
-
E.
paternalTitleConnection
Indicates a relationship where one entity holds a paternal (father-related) title in connection to another entity.
- F. None of above. chosen
Provenance (4 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_69e11e3e0c7c8190b30d278845e2497e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aa8f178819094d1556df5aee5b9 |
completed | April 28, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:35 p.m.