Triple
T5475587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Radicalism of the American Revolution |
E122943
|
entity |
| Predicate | setInPeriodDescribed |
P56370
|
FINISHED |
| Object | 18th-century America |
—
|
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: 18th-century America | Statement: [The Radicalism of the American Revolution, setInPeriodDescribed, 18th-century America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setInPeriodDescribed Context triple: [The Radicalism of the American Revolution, setInPeriodDescribed, 18th-century America]
-
A.
isSetInTimePeriod
chosen
Indicates that an event, story, or situation takes place within a specified time period.
-
B.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
C.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
D.
periodizedAs
Indicates that something has been divided or organized into distinct time periods according to a particular periodization scheme.
-
E.
usePeriodStart
Indicates that an entity begins to be used or becomes active starting from a specified time period.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd923465c88190ad9c1b75b268f7ca |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.