Triple
T11005745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Major Archiepiscopal Church |
E260113
|
entity |
| Predicate | hasRightsSimilarTo |
P96959
|
FINISHED |
| Object | patriarchal church |
—
|
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 church | Statement: [Major Archiepiscopal Church, hasRightsSimilarTo, patriarchal church]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightsSimilarTo Context triple: [Major Archiepiscopal Church, hasRightsSimilarTo, patriarchal church]
-
A.
hasRightsOver
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
B.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or resource.
-
C.
hasSimilarityTo
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
D.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
E.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
- 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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797562de4819097a0e136180d283a |
completed | April 9, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69d72e96be6c8190a46c69f61b2d8cd4 |
completed | April 9, 2026, 4:44 a.m. |
| PDg | Predicate description generation | batch_69d733b27ffc81908ab1b8df198cd5c7 |
completed | April 9, 2026, 5:05 a.m. |
Created at: April 8, 2026, 9:25 p.m.