Triple
T28919910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vega$ |
E733479
|
entity |
| Predicate | notableSettingFeature |
P61000
|
FINISHED |
| Object | Las Vegas Strip casinos |
E49454
|
NE 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: Las Vegas Strip casinos | Statement: [Vega$, notableSettingFeature, Las Vegas Strip casinos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSettingFeature Context triple: [Vega$, notableSettingFeature, Las Vegas Strip casinos]
-
A.
notableSetting
Indicates that a particular place or environment is especially significant or prominent as the context in which an entity is situated or occurs.
-
B.
notableSettingType
Indicates that one entity is a prominent or characteristic type of setting or environment associated with another entity.
-
C.
notableFeat
Indicates that an entity is recognized for having achieved or performed a particularly significant or distinguished feat.
-
D.
notableFeatureOn
chosen
Indicates that one entity is a prominent or distinguishing feature located on or part of another entity.
-
E.
notableTechnicalFeature
Indicates that an entity possesses a significant or distinguishing technical characteristic or capability.
- F. None of above.
Provenance (4 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a01b841f5508190832bba00cf795bad |
completed | May 11, 2026, 11:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a24d41d69188190a3a8b43a6649662d |
completed | June 7, 2026, 2:14 a.m. |
| PD | Predicate disambiguation | batch_6a01b59541fc8190a9b13a55327c4aa1 |
completed | May 11, 2026, 10:55 a.m. |
Created at: April 28, 2026, 8:18 a.m.