Triple
T34572323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tevul Yom |
E887656
|
entity |
| Predicate | definesStatusFor |
P101079
|
FINISHED |
| Object | person who immersed that day |
—
|
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: person who immersed that day | Statement: [Tevul Yom, definesStatusFor, person who immersed that day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesStatusFor Context triple: [Tevul Yom, definesStatusFor, person who immersed that day]
-
A.
definedStatusFor
chosen
Indicates that one entity establishes or specifies the status or state assigned to another entity.
-
B.
regulatedStatusOf
Indicates that one entity has regulatory authority or control over the status or condition of another entity.
-
C.
isStatusOf
Indicates that a particular status or condition is assigned to, or characterizes, a specific entity.
-
D.
recognizesStatus
Indicates that one entity acknowledges or accepts the official status or standing of another entity.
-
E.
governsStatusOf
Indicates that one entity has authority or control over determining or regulating the status or condition of 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_69f349d1a5fc81908557a46875b2f157 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fe991bca608190b524e419642f4243 |
completed | May 9, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69fe979fc1c4819091fc48d63ea12063 |
completed | May 9, 2026, 2:10 a.m. |
Created at: May 1, 2026, 2:03 a.m.