Triple
T28571117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melkite Greek Catholic bishops |
E723116
|
entity |
| Predicate | shareDoctrineWith |
P87214
|
FINISHED |
| Object | Roman Catholic 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: Roman Catholic bishops | Statement: [Melkite Greek Catholic bishops, shareDoctrineWith, Roman Catholic bishops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareDoctrineWith Context triple: [Melkite Greek Catholic bishops, shareDoctrineWith, Roman Catholic bishops]
-
A.
sharesDoctrine
chosen
Indicates that two entities adhere to or promote the same doctrine, belief system, or set of principles.
-
B.
sharesModuleWith
Indicates that two entities are associated with or participate in at least one common module.
-
C.
sharesDamWith
Indicates that two entities are impounded or regulated by the same dam structure.
-
D.
alternativeDoctrine
Indicates that one doctrine serves as an alternative or substitute to another doctrine within a given context.
-
E.
sharesUniverseWith
Indicates that two entities exist within the same fictional or narrative universe, implying shared continuity, setting, or canon.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: April 28, 2026, 4:09 a.m.