Triple
T62671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Original sin |
E1243
|
entity |
| Predicate | ordinarilyAddressedBy |
P86
|
FINISHED |
| Object | baptism (in many traditions) |
—
|
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: baptism (in many traditions) | Statement: [Original sin, ordinarilyAddressedBy, baptism (in many traditions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ordinarilyAddressedBy Context triple: [Original sin, ordinarilyAddressedBy, baptism (in many traditions)]
-
A.
usesAddressingSystem
Indicates that one entity employs or applies a particular addressing system associated with another entity.
-
B.
attendedBy
Indicates that an event, place, or activity is participated in or visited by a particular person or group.
-
C.
governmentBodyAddressed
Indicates that a particular government body is the one being directly addressed or targeted by a communication, action, or request.
-
D.
administeredBy
chosen
Indicates that an action, service, or process is carried out, managed, or overseen by a specified agent or authority.
-
E.
address
Indicates that one entity directs spoken or written communication specifically to 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_69a24ba4f760819081f6638a3c70538a |
completed | Feb. 28, 2026, 1:57 a.m. |
| NER | Named-entity recognition | batch_69a251f74b0881909ad89127b8171277 |
completed | Feb. 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69a24ea242c8819086fe00bf01e6523e |
completed | Feb. 28, 2026, 2:10 a.m. |
Created at: Feb. 28, 2026, 2:02 a.m.