Triple
T2058019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruthenian Greek Catholic Church |
E45720
|
entity |
| Predicate | preservesOwnLaw |
P35506
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Ruthenian Greek Catholic Church, preservesOwnLaw, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preservesOwnLaw Context triple: [Ruthenian Greek Catholic Church, preservesOwnLaw, true]
-
A.
obeysLaw
Indicates that an entity follows, complies with, or acts in accordance with a specified law or set of laws.
-
B.
typeOfPreservationLaw
Indicates the specific category or kind of preservation law that governs how something is protected or conserved.
-
C.
enforcedLaw
Indicates that an authority actively applies or upholds a specific law to regulate behavior or resolve situations.
-
D.
containsLawOn
Indicates that one entity (such as a document, code, or regulation) includes or sets forth legal provisions concerning another entity or subject.
-
E.
preservesFeature
Indicates that one entity maintains or keeps intact a particular feature, property, or characteristic of another entity during some process or interaction.
- 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_69a8891a19508190a12ef1e192308dcb |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb9ae0130819089f7d62005466a45 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7ad5a7c8190b92575d6053b3fb7 |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb92f90a881909a1f10b060132a9e |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:40 p.m.