Triple
T904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | As We May Think |
E17
|
entity |
| Predicate | timePeriodDescribed |
P106
|
FINISHED |
| Object | future of science after World War II |
—
|
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: future of science after World War II | Statement: [As We May Think, timePeriodDescribed, future of science after World War II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timePeriodDescribed Context triple: [As We May Think, timePeriodDescribed, future of science after World War II]
-
A.
focusPeriod
chosen
Indicates the specific time span during which attention, activity, or analysis is concentrated on something.
-
B.
wasDevelopedInPeriod
Indicates that something was created, produced, or brought into existence during a specified time period.
-
C.
locatedInTimeZone
Indicates that an entity exists or an event occurs within the temporal bounds defined by a specific time zone.
-
D.
frequency
Indicates how often an event, action, or relationship occurs within a given period or context.
-
E.
publicationYear
Indicates the specific calendar year in which a work was formally published or released.
- 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_69a22a285828819081a58308fb963df1 |
completed | Feb. 27, 2026, 11:35 p.m. |
| NER | Named-entity recognition | batch_69a23211f05c8190b8deb03a8540d84d |
completed | Feb. 28, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69a230c2c48481908beb1db3cc9768aa |
completed | Feb. 28, 2026, 12:03 a.m. |
Created at: Feb. 27, 2026, 11:36 p.m.