Triple
T20028588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Michael Portier |
E495056
|
entity |
| Predicate | officeStartForBishopOfMobile |
P1383
|
FINISHED |
| Object | 1829 |
—
|
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: 1829 | Statement: [Michael Portier, officeStartForBishopOfMobile, 1829]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officeStartForBishopOfMobile Context triple: [Michael Portier, officeStartForBishopOfMobile, 1829]
-
A.
coBishopWith
Indicates that two individuals hold the office of bishop concurrently within the same ecclesiastical context or jurisdiction.
-
B.
officeStartAsPontifexMaximus
Indicates the point in time when an individual begins their tenure in the office of Pontifex Maximus.
-
C.
officeStartFor
Indicates the time or date at which an entity begins its term, role, or period of service in an office or official position.
-
D.
currentBishop
Indicates that one entity currently holds the position or role of bishop with respect to another entity (such as a diocese or church).
-
E.
officeStart
chosen
Indicates the time or date at which an entity’s term, role, or period of holding office begins.
- 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_69da626bfd288190aa5d65098b6433ae |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6628f67e081909b9e69dfbe2127ce |
completed | April 20, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69e54ce752748190a0a1ffddd0372271 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:36 p.m.