Triple
T6018526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tobias |
E134005
|
entity |
| Predicate | textStatus |
P68792
|
FINISHED |
| Object | deuterocanonical book protagonist |
—
|
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: deuterocanonical book protagonist | Statement: [Tobias, textStatus, deuterocanonical book protagonist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textStatus Context triple: [Tobias, textStatus, deuterocanonical book protagonist]
-
A.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
B.
titleStatus
Indicates the current legal or administrative state of a title (such as ownership, validity, or processing stage) in relation to an entity or record.
-
C.
originalTextStatus
Indicates the relationship between a text and its current state or condition relative to its original, unmodified form.
-
D.
statusIndicates
Indicates that a particular status value conveys or reflects the current condition, state, or situation of an entity or process.
-
E.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
- 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_69c008742a5c8190b9cb9c2787a3d8b3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f8589d0819089ae7840461640f6 |
completed | March 22, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69c049e75b3881908be106fbcf8c68d4 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8c5bfc8190b986a7071d1b23e3 |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:07 p.m.