Triple
T8501396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go Set a Watchman |
E201224
|
entity |
| Predicate | timeBetweenWritingAndPublication |
P42825
|
FINISHED |
| Object | over 50 years |
—
|
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: over 50 years | Statement: [Go Set a Watchman, timeBetweenWritingAndPublication, over 50 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeBetweenWritingAndPublication Context triple: [Go Set a Watchman, timeBetweenWritingAndPublication, over 50 years]
-
A.
timeFromEventToPublication
chosen
Indicates the duration between when an event occurs and when it is published or reported.
-
B.
timeLagBetweenPublicationAndAward
Indicates the duration of time that passes between when something is published and when it receives an award.
-
C.
publicationPeriod
Indicates the span of time during which something is published, active in publication, or valid as a published work.
-
D.
epochAtPublication
Indicates the specific time or epoch at which the publication event occurs or is recorded.
-
E.
timeInPublicationOrder
Indicates the chronological position or sequence of an item as it appears in the order in which related works were originally published.
- 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_69ca831fe47c8190b5c57b456d2aefa0 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe59ad65c8190a2b8e6d22269853a |
completed | March 31, 2026, 3:17 p.m. |
| PD | Predicate disambiguation | batch_69cbd10a4b0881909e254117780dc823 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:14 p.m.