Triple
T1433252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Theophilus |
E30497
|
entity |
| Predicate | textualStatus |
P4091
|
FINISHED |
| Object | otherwise unknown outside Luke–Acts |
—
|
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: otherwise unknown outside Luke–Acts | Statement: [Theophilus, textualStatus, otherwise unknown outside Luke–Acts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: textualStatus Context triple: [Theophilus, textualStatus, otherwise unknown outside Luke–Acts]
-
A.
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.
-
B.
originalTextStatus
chosen
Indicates the relationship between a text and its current state or condition relative to its original, unmodified form.
-
C.
exportStatus
Indicates the current state or outcome of an entity’s export process (e.g., pending, in progress, completed, or failed).
-
D.
status
Indicates the current condition, state, or standing of an entity within a given context.
-
E.
communicationStatus
Indicates the current state or condition of a communication process or exchange between entities (e.g., pending, active, failed, completed).
- 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_69a498fc69ec8190b61722bd4b67c4d2 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c500a9888190a16fbb1ec97a79c9 |
completed | March 1, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69a4c4771c9481908ae47c959debbe77 |
completed | March 1, 2026, 10:57 p.m. |
Created at: March 1, 2026, 8 p.m.