Triple
T11572275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western |
E274418
|
entity |
| Predicate | hasTypicalTimePeriod |
P56370
|
FINISHED |
| Object | 19th-century American West |
—
|
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: 19th-century American West | Statement: [Western, hasTypicalTimePeriod, 19th-century American West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalTimePeriod Context triple: [Western, hasTypicalTimePeriod, 19th-century American West]
-
A.
typicalPeriod
Indicates the usual or characteristic time interval or duration associated with an event, process, or state.
-
B.
hasTypicalUseTime
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
C.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
D.
hasPeriodRange
Indicates that there is a temporal span or interval during which something is valid, active, or applicable.
-
E.
isSetInTimePeriod
chosen
Indicates that an event, story, or situation takes place within 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd6913881908becf188c0a7a275 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dcbacd0819094d4a1237055affa |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.