Triple
T16321291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arian controversy |
E396296
|
entity |
| Predicate | positionRejected |
P122693
|
FINISHED |
| Object | the Son is a created being |
—
|
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: the Son is a created being | Statement: [Arian controversy, positionRejected, the Son is a created being]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionRejected Context triple: [Arian controversy, positionRejected, the Son is a created being]
-
A.
rejectedIn
Indicates that an entity or proposal was not accepted or was turned down within a specific context, process, or location.
-
B.
rejectedBy
Indicates that one entity has been refused, dismissed, or not accepted by another entity.
-
C.
rejectedAt
Indicates the time or date at which something (such as a request, application, or proposal) was formally rejected.
-
D.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
E.
rejectedFromEvent
Indicates that an entity was denied participation in, or access to, a particular event.
- 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_69d87f255b788190a400eba031dd85d8 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e296b5f0f081909a5379deaf0df5d5 |
completed | April 17, 2026, 8:23 p.m. |
| PD | Predicate disambiguation | batch_69e219fc72c881909d452274e7af8238 |
completed | April 17, 2026, 11:31 a.m. |
| PDg | Predicate description generation | batch_69e21e56e0348190a3d9475360231a70 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:06 a.m.