Triple
T47878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicene Creed |
E940
|
entity |
| Predicate | authorityStatus |
P2231
|
FINISHED |
| Object | ecumenical creed |
—
|
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: ecumenical creed | Statement: [Nicene Creed, authorityStatus, ecumenical creed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authorityStatus Context triple: [Nicene Creed, authorityStatus, ecumenical creed]
-
A.
authority
Indicates that one entity has the power, right, or official capacity to direct, control, or make decisions for another entity or over a particular domain.
-
B.
hasAuthorityStatus
chosen
Indicates that one entity holds a particular level or type of official power, control, or decision-making authority over another entity or within a defined context.
-
C.
styleGranted
Indicates that a particular style, manner, or mode of expression has been conferred or authorized for use by one entity to another.
-
D.
grantedBy
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
E.
grantedTo
Indicates that a right, permission, or resource has been formally given or assigned by one party to another.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c1a5c14819088748317a3f262c8 |
completed | Feb. 28, 2026, 1:59 a.m. |
| PD | Predicate disambiguation | batch_69a24abe7cb481908d969e54032f6c75 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.