Triple
T158159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Arianism |
E3222
|
entity |
| Predicate | historicalDebate |
P4530
|
FINISHED |
| Object | Arian controversy |
—
|
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: Arian controversy | Statement: [Arianism, historicalDebate, Arian controversy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalDebate Context triple: [Arianism, historicalDebate, Arian controversy]
-
A.
historicallyContestedBy
Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
-
B.
debatedAt
chosen
Indicates that a debate or formal discussion involving the subject took place at the specified location or event.
-
C.
historicalAssessment
Indicates an evaluation or judgment of something based on its historical context, significance, or development over time.
-
D.
historicalImpact
Indicates the influence or lasting effects that an entity, event, or action has had on subsequent history or historical developments.
-
E.
historicalClaim
Indicates that an entity asserts or presents a statement about past events or conditions as a matter of historical fact.
- 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a2565f30848190a2a71fdb7dc140b5 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.