Triple
T24711079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Emperor’s Soul |
E612027
|
entity |
| Predicate | timeToWriteClaimedByAuthor |
P125076
|
FINISHED |
| Object | about two weeks |
—
|
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: about two weeks | Statement: [The Emperor’s Soul, timeToWriteClaimedByAuthor, about two weeks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeToWriteClaimedByAuthor Context triple: [The Emperor’s Soul, timeToWriteClaimedByAuthor, about two weeks]
-
A.
timeframeClaimedForSingularity
Indicates that an entity asserts or specifies a particular period of time in which a technological or singularity event is expected to occur.
-
B.
claimAboutTime
Indicates that one entity makes a statement or assertion specifically concerning a point or interval in time.
-
C.
timeToWriteApprox
chosen
Indicates an approximate amount of time required to write or produce the associated content or work.
-
D.
standByTimeClaimed
Indicates that a standby or waiting time has been reported or asserted for a given entity or event.
-
E.
dateClaimedInDescription
Indicates that a date mentioned in a textual description is asserted or claimed as relevant to the subject.
- 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_69e2c4d9c24c8190a3712d74327f0c6e |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 3:24 a.m.