Triple
T12962649
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlas of North American English |
E321181
|
entity |
| Predicate | dataCollectionPeriod |
P9341
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Atlas of North American English, dataCollectionPeriod, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataCollectionPeriod Context triple: [Atlas of North American English, dataCollectionPeriod, 1990s]
-
A.
collectionTimespan
chosen
Indicates the time period over which a collection exists, is accumulated, or is considered valid.
-
B.
dataCollectedOn
Indicates that certain data was gathered, recorded, or measured at a specific point in time or on a particular date.
-
C.
typicalCollectionPeriodStart
Indicates the date or point in time when a standard or customary collection period begins.
-
D.
timePeriod
Indicates the specific span or interval of time during which an event, state, or relationship occurs or is valid.
-
E.
documentationPeriod
Indicates the time span or interval during which something is documented, recorded, or valid in the documentation.
- 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_69d80763bd6c819094437da5b20b01d2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d97e59a4c88190907d05b8d57dae89 |
completed | April 10, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69d97dba57988190b786ffed55687a72 |
completed | April 10, 2026, 10:46 p.m. |
Created at: April 9, 2026, 8:23 p.m.