Triple
T2545027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishop of Córdoba |
E57877
|
entity |
| Predicate | mayHaveAuxiliary |
P9417
|
FINISHED |
| Object | auxiliary bishops |
—
|
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: auxiliary bishops | Statement: [Archbishop of Córdoba, mayHaveAuxiliary, auxiliary bishops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayHaveAuxiliary Context triple: [Archbishop of Córdoba, mayHaveAuxiliary, auxiliary bishops]
-
A.
hasAuxiliaryRole
Indicates that an entity serves in a supporting or secondary capacity to another entity or primary role.
-
B.
mayHold
chosen
Indicates that one entity is permitted or allowed to possess, contain, or maintain another entity.
-
C.
mayResultIn
Indicates that one entity has the potential to cause, lead to, or bring about another entity or outcome, without guaranteeing that it will occur.
-
D.
canAlsoBe
Indicates that something has an additional possible state, role, or classification beyond its primary one.
-
E.
mayHead
Indicates that an entity is permitted or eligible to serve as the leader or head of another entity.
- 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_69ab4a5212d88190b989ce129f2ad87f |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd2c285288190b41fc0188879623a |
completed | March 7, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69abd0c63964819092d5f578195ae8dd |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:47 p.m.