Triple
T327448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | First Council of Nicaea |
E6549
|
entity |
| Predicate | forbade |
P272
|
FINISHED |
| Object | celebrating Easter on the Jewish Passover |
—
|
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: celebrating Easter on the Jewish Passover | Statement: [First Council of Nicaea, forbade, celebrating Easter on the Jewish Passover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forbade Context triple: [First Council of Nicaea, forbade, celebrating Easter on the Jewish Passover]
-
A.
prohibits
chosen
Indicates that one entity forbids or disallows another entity from performing a specific action or being in a certain state.
-
B.
bannedBy
Indicates that an entity is prohibited or disallowed as a result of a decision or action taken by another entity.
-
C.
discourages
Indicates an action or influence that deters, dissuades, or reduces the likelihood of someone performing a particular behavior or pursuing a certain outcome.
-
D.
forcedBy
Indicates that an entity is compelled or coerced into an action or state by another entity.
-
E.
condemnedBy
Indicates that an entity is judged, denounced, or declared wrong or unacceptable by another entity.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea98fa2c8190a5b44f4a26543a17 |
completed | Feb. 28, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69a2e94aab1c8190b8654708c87eeb91 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.