Triple
T27192821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Red Book |
E683518
|
entity |
| Predicate | completedSubstantiallyBy |
P108008
|
FINISHED |
| Object | circa 1930 |
—
|
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: circa 1930 | Statement: [The Red Book, completedSubstantiallyBy, circa 1930]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: completedSubstantiallyBy Context triple: [The Red Book, completedSubstantiallyBy, circa 1930]
-
A.
completedIn
Indicates that an action, process, or task was fully finished within a specified time period or duration.
-
B.
completedBy
Indicates that a task, process, or action has been finished or carried out by a particular entity.
-
C.
completedAfter
Indicates that one event or task was finished at a later time than another specified event or task.
-
D.
completedBefore
Indicates that one event or action was fully completed prior to the start or completion of another specified event or action.
-
E.
substantialCompletionDate
chosen
Indicates the date on which a project, work, or obligation is considered substantially complete, meaning the main required work has been finished to the point it can be used for its intended purpose.
- 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_69eefad1fd5c8190a4a46ea6afe58bfa |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 9:33 a.m.