Triple
T32405216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Easter controversy |
E828057
|
entity |
| Predicate | earlierRelatedEvent |
P45313
|
FINISHED |
| Object | Quartodeciman controversy |
—
|
NE NERFINISHED |
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: Quartodeciman controversy | Statement: [Easter controversy, earlierRelatedEvent, Quartodeciman controversy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earlierRelatedEvent Context triple: [Easter controversy, earlierRelatedEvent, Quartodeciman controversy]
-
A.
laterRelatedEvent
Indicates that one event is temporally related to another by occurring at a later time.
-
B.
closelyAssociatedEvent
Indicates that one event is strongly related to, connected with, or occurs in close conjunction with another event.
-
C.
earlierAct
chosen
Indicates that one action or event occurred before another in time.
-
D.
similarEvent
Indicates that one event resembles another in relevant characteristics, context, or outcomes.
-
E.
associatedEpicEvent
Indicates that one entity is linked or connected to a particular epic event in a relevant or meaningful way.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: May 1, 2026, 12:53 a.m.