Triple
T84603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holy Eucharist |
E1701
|
entity |
| Predicate | normallyReceivedBy |
P1509
|
FINISHED |
| Object | baptized Christians |
—
|
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: baptized Christians | Statement: [Holy Eucharist, normallyReceivedBy, baptized Christians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normallyReceivedBy Context triple: [Holy Eucharist, normallyReceivedBy, baptized Christians]
-
A.
receivedSupportFrom
Indicates that one entity obtained help, resources, or backing from another entity.
-
B.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
C.
notableRecipient
Indicates that an entity has received a notable award, honor, or recognition from another entity.
-
D.
attendedBy
chosen
Indicates that an event, place, or activity is participated in or visited by a particular person or group.
-
E.
givenTo
Indicates that something is transferred or presented by one entity to another as a recipient.
- 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_69a24c8150408190910a693eb51c1f71 |
completed | Feb. 28, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69a24f4e73c081908d2da146226ef05e |
completed | Feb. 28, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69a24eb469548190b38c24e81f36c838 |
completed | Feb. 28, 2026, 2:11 a.m. |
Created at: Feb. 28, 2026, 2:06 a.m.