Triple
T4399298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pentarchy |
E99572
|
entity |
| Predicate | seeStatus |
P55449
|
FINISHED |
| Object | patriarchal sees |
—
|
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: patriarchal sees | Statement: [Pentarchy, seeStatus, patriarchal sees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seeStatus Context triple: [Pentarchy, seeStatus, patriarchal sees]
-
A.
seeksStatusAs
Indicates that one entity is attempting to obtain or be recognized with a particular status, role, or standing in relation to another entity.
-
B.
isSeeOf
Indicates that one entity serves as the episcopal or ecclesiastical seat (see) of another, typically a bishop or similar religious office.
-
C.
loreStatus
Indicates the canonical or contextual standing of something within a fictional or narrative universe (such as whether it is official, speculative, or non-canonical lore).
-
D.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
- 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_69b345506b408190b0e3dee616738a7d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b352cc4ab081908bc45d2f76cd4da8 |
completed | March 12, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69b34f597998819092477efdedb51427 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b34ff7018c81908ad8597e525c042b |
completed | March 12, 2026, 11:44 p.m. |
Created at: March 12, 2026, 11:20 p.m.