Triple
T28681733
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Open Orthodoxy |
E726024
|
entity |
| Predicate | isDefendedBySupportersAs |
P21338
|
FINISHED |
| Object | authentically Orthodox |
—
|
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: authentically Orthodox | Statement: [Open Orthodoxy, isDefendedBySupportersAs, authentically Orthodox]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDefendedBySupportersAs Context triple: [Open Orthodoxy, isDefendedBySupportersAs, authentically Orthodox]
-
A.
isDefendedOn
Indicates that one entity provides protection, justification, or support for another entity in a specific context or situation.
-
B.
defendedAs
chosen
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
C.
titleDefendedBy
Indicates that a specific title or championship is actively defended or held against challengers by a particular entity.
-
D.
hasSupportersIn
Indicates that an entity is backed or endorsed by people or groups located within a specified place or region.
-
E.
isDefendedAt
Indicates that a particular entity is protected or justified at a specific time, place, or context.
- 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_69f01d867608819086bc3e6b4f9de866 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f658ee40088190b71e1219407690d0 |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 5:09 a.m.