Triple
T25578046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act IV (Faust, Part Two) |
E641164
|
entity |
| Predicate | workDateCompleted |
P90615
|
FINISHED |
| Object | early 19th century |
—
|
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: early 19th century | Statement: [Act IV (Faust, Part Two), workDateCompleted, early 19th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workDateCompleted Context triple: [Act IV (Faust, Part Two), workDateCompleted, early 19th century]
-
A.
workCompletedAfter
Indicates that one entity’s work or task was finished at a later time than another specified work or task.
-
B.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
C.
associatedWorkDate
chosen
Indicates the date on which a related or associated work (such as a publication, performance, or creation) is linked to the subject entity.
-
D.
originalCompletionDate
Indicates the date on which something was first completed, before any subsequent changes, revisions, or updates.
-
E.
completionDateBranch
Indicates the date on which a specific branch or version of something is completed or finalized.
- 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_69e75dc281bc819095ec04dc0c3a94d0 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f931bdd88190ac4bf404087f4c83 |
completed | May 2, 2026, 1:16 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 4:02 p.m.