Triple
T24842439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mid-Pentecost |
E621650
|
entity |
| Predicate | connectedFeast |
P134131
|
FINISHED |
| Object | Pentecost |
—
|
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: Pentecost | Statement: [Mid-Pentecost, connectedFeast, Pentecost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectedFeast Context triple: [Mid-Pentecost, connectedFeast, Pentecost]
-
A.
traditionalFeastConnection
Indicates a relationship in which entities are linked through the observance, organization, or shared participation in a traditional feast or ceremonial meal.
-
B.
feastFollows
Indicates that a feast or celebratory meal occurs after and as a consequence of a preceding event or action.
-
C.
feastOf
Indicates that one entity is the religious or ceremonial feast day associated with another entity (such as a person, event, or deity).
-
D.
extendedFeast
Indicates a situation where a feast or celebratory meal continues for an unusually long or prolonged period of time.
-
E.
feastRelatedTo
chosen
Indicates a relationship in which one entity is connected or relevant to a feast, such as by association, participation, context, or thematic linkage.
- 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_69e2fac185d48190a0a6073ad1f6b792 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 5:19 a.m.