Triple
T22224334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Las Vegas |
E549294
|
entity |
| Predicate | hasNotableTimePeriodContext |
P116486
|
FINISHED |
| Object | 20th century |
—
|
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: 20th century | Statement: [Mr. Las Vegas, hasNotableTimePeriodContext, 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTimePeriodContext Context triple: [Mr. Las Vegas, hasNotableTimePeriodContext, 20th century]
-
A.
hasNotabilityPeriod
chosen
Indicates the time span during which an entity is or was notable or prominent.
-
B.
hasNotableRecordingPeriod
Indicates that an entity is associated with a specific time span during which notable recording activity took place.
-
C.
hasHistoryPeriod
Indicates that something is associated with, belongs to, or occurs within a specific historical period or era.
-
D.
notableEventPeriod
Indicates the time span during which a notable or significant event associated with an entity took place.
-
E.
hasDateContext
Indicates that something is associated with, constrained by, or interpreted within a specific date or time-related context.
- 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_69e11e403d6481909a94d0aaf157f6ef |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b93e2208190aee70ffd82962ea0 |
completed | April 28, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.