Triple
T17269440
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicodemus |
E419213
|
entity |
| Predicate | defendsJesus |
P6876
|
FINISHED |
| Object | before the Pharisees |
—
|
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: before the Pharisees | Statement: [Nicodemus, defendsJesus, before the Pharisees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defendsJesus Context triple: [Nicodemus, defendsJesus, before the Pharisees]
-
A.
defends
chosen
Indicates that one entity protects or supports another entity against attack, criticism, or harm.
-
B.
theologicalDefenseBy
Indicates a relationship where one entity provides a theological justification, argument, or defense on behalf of another entity, doctrine, or position.
-
C.
defendedOn
Indicates that one entity protected, supported, or argued in favor of another entity during a specific time or event.
-
D.
defendedAs
Indicates that one entity is presented, argued, or justified as being equivalent to or serving the role of another entity in a defensive or protective context.
-
E.
titleDefendedBy
Indicates that a specific title or championship is actively defended or held against challengers by a particular 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4803b48190894b3bb9a4970602 |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832a284481908a8a3da7ac91de5a |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.