Triple
T32063272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joy McNally |
E818803
|
entity |
| Predicate | cityOfKeyEvents |
P127335
|
FINISHED |
| Object | Las Vegas |
—
|
NE NERFINISHED |
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: Las Vegas | Statement: [Joy McNally, cityOfKeyEvents, Las Vegas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cityOfKeyEvents Context triple: [Joy McNally, cityOfKeyEvents, Las Vegas]
-
A.
focusCityHistory
Indicates that there is a historical or context-defining relationship between a focal city and its past events, developments, or status.
-
B.
significantEventPlace
chosen
Indicates the place where a significant event occurred or is associated with an entity.
-
C.
capitalOrMajorCityHistorically
Indicates that a place has historically served as a capital or as a major, centrally important city for a political or cultural entity.
-
D.
cityOfSecondMajorEvent
Indicates the city where the second major event in a sequence or series takes place.
-
E.
locationGaveRiseTo
Indicates that a particular location is the origin or source from which something (such as an event, movement, phenomenon, or entity) emerged or developed.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4f757788190b3f55d91289b7fc1 |
completed | May 3, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a7bdb481908d16a32f49e38c2c |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:22 a.m.