Triple
T337990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Feast in Eastern Christianity |
E6769
|
entity |
| Predicate | oftenFollowedBy |
P134
|
FINISHED |
| Object | afterfeast |
—
|
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: afterfeast | Statement: [Great Feast in Eastern Christianity, oftenFollowedBy, afterfeast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenFollowedBy Context triple: [Great Feast in Eastern Christianity, oftenFollowedBy, afterfeast]
-
A.
follows
chosen
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
B.
followsWork
Indicates that one work (such as a publication, version, or creative piece) comes directly after another in sequence or succession.
-
C.
followsStage
Indicates that one stage occurs after and in sequence with another stage in a process or workflow.
-
D.
establishedFollowing
Indicates that one entity created or set up another entity after, and in consequence of, a prior entity or event.
-
E.
followedByRoleInCareerOf
Indicates that one role or position directly succeeds another in the sequence of roles within a single entity’s career.
- 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae23b0c819081f8bf9ac26685ab |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.