Triple
T16789423
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book XX |
E408065
|
entity |
| Predicate | treatsAsAuthority |
P79128
|
FINISHED |
| Object | Holy Scripture |
—
|
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: Holy Scripture | Statement: [Book XX, treatsAsAuthority, Holy Scripture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsAsAuthority Context triple: [Book XX, treatsAsAuthority, Holy Scripture]
-
A.
usesAuthorityOf
Indicates that one entity exercises power, rights, or influence derived from or on behalf of another entity’s authority.
-
B.
usedAsAuthorityFor
chosen
Indicates that one entity is relied upon as an authoritative source or reference for validating, justifying, or supporting another entity.
-
C.
recognizesAuthority
Indicates that one entity accepts, acknowledges, or submits to the power, control, or legitimate decision-making role of another entity.
-
D.
indicatesAuthorityOver
Indicates that one entity holds recognized power, control, or decision-making authority over another entity.
-
E.
authoritativeFor
Indicates that one entity has recognized control, responsibility, or decision-making power over another entity or domain.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a50e18819090a30e1f38e520e0 |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:22 a.m.