Triple
T25622280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E. Parry Thomas |
E642330
|
entity |
| Predicate | notablePersonIn |
P185613
|
FINISHED |
| Object | history of Las Vegas, Nevada |
—
|
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: history of Las Vegas, Nevada | Statement: [E. Parry Thomas, notablePersonIn, history of Las Vegas, Nevada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notablePersonIn Context triple: [E. Parry Thomas, notablePersonIn, history of Las Vegas, Nevada]
-
A.
notablePublicFigure
Indicates that the subject is widely recognized and holds a significant public profile or influence in society.
-
B.
notablePersonDiscussed
Indicates that the subject entity includes or features a discussion about the referenced notable person.
-
C.
notableIndividuals
chosen
Indicates that certain individuals are recognized as particularly important, famous, or influential in relation to something.
-
D.
namedForNotablePersonFrom
Indicates that one entity is named in honor of a notable person who originates from another specified place or group.
-
E.
namedPersonNotableFor
Indicates that a person is especially known or recognized for a particular work, role, achievement, or characteristic.
- 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_69e77e7a96748190b10f2699041e4e43 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69fd474b7e788190a9bb9b542d878f60 |
completed | May 8, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69fd46d8b2f0819099d92d72c902f60e |
completed | May 8, 2026, 2:13 a.m. |
Created at: April 21, 2026, 5:05 p.m.