Triple
T4129447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishop of Urgell |
E85003
|
entity |
| Predicate | termLengthAsCoPrince |
P540
|
FINISHED |
| Object | life tenure (while bishop) |
—
|
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: life tenure (while bishop) | Statement: [Bishop of Urgell, termLengthAsCoPrince, life tenure (while bishop)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: termLengthAsCoPrince Context triple: [Bishop of Urgell, termLengthAsCoPrince, life tenure (while bishop)]
-
A.
reignDuration
Indicates the length of time during which an entity held ruling or governing authority over a domain or group.
-
B.
coPrince
Indicates a relationship in which two or more individuals simultaneously share and exercise the rank and authority of prince over the same domain or polity.
-
C.
termLength
chosen
Indicates the duration or period of time for which an agreement, position, or condition remains in effect.
-
D.
monarchDuringTerm
Indicates that a specified monarch was the reigning sovereign during the time span of a given officeholder’s term.
-
E.
periodOfRule
Indicates the span of time during which an entity exercised authority, control, or governance over something.
- 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_69aed935ccd881909dc61f81bcdb7a78 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03a0f3408190adba7a8513bd3d12 |
completed | March 9, 2026, 5:30 p.m. |
| PD | Predicate disambiguation | batch_69af01883b6c8190a482ead589a131a5 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:42 p.m.