Triple
T16736461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uzziah |
E406729
|
entity |
| Predicate | sin |
P124446
|
FINISHED |
| Object | entered the temple to burn incense |
—
|
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: entered the temple to burn incense | Statement: [Uzziah, sin, entered the temple to burn incense]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sin Context triple: [Uzziah, sin, entered the temple to burn incense]
-
A.
son
Indicates a familial relationship where one entity is the male child of another entity.
-
B.
side
Indicates that one entity is located at, aligned with, or associated with the lateral part or edge of another entity.
-
C.
is
Indicates that two entities are equivalent, share an attribute, or stand in a specified state or relation to each other.
-
D.
silent
Indicates that an entity produces no audible sound or refrains from speaking or making noise.
-
E.
by
Indicates that an action is performed, caused, or authored through the agency, means, or proximity of a specified entity.
- F. None of above. chosen
Provenance (4 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3a86848190a03f243dd1bdb899 |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.