Triple
T23974127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Suffragan Bishop of Long Island |
E604314
|
entity |
| Predicate | seeAlsoOffice |
P9115
|
FINISHED |
| Object | Bishop of Long Island |
—
|
NE NERFINISHED |
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: Bishop of Long Island | Statement: [Suffragan Bishop of Long Island, seeAlsoOffice, Bishop of Long Island]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeAlsoOffice Context triple: [Suffragan Bishop of Long Island, seeAlsoOffice, Bishop of Long Island]
-
A.
relatesToOffice
Indicates that one entity has a connection, association, or relevance to an office, its functions, or its environment.
-
B.
equivalentOffice
Indicates that two offices are considered functionally or formally the same position, role, or authority, even if they differ in name or jurisdiction.
-
C.
includedOffice
Indicates that one office is contained within, or forms part of, another office or organizational unit.
-
D.
otherOffice
chosen
Indicates that one office is an alternative or additional office associated with the same organization, person, or entity as another office.
-
E.
officeIs
Indicates that one entity serves as the office or official workplace location 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_69e29543019c8190872462e593cc50b4 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f1d1de6ee081908590e438012e96bd |
completed | April 29, 2026, 9:39 a.m. |
| PD | Predicate disambiguation | batch_69f161578d54819084a8b35496299993 |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 9:26 p.m.