Triple
T29520005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mandalay Resort Group |
E748905
|
entity |
| Predicate | hadKeyBusinessActivity |
P48385
|
FINISHED |
| Object | casino operation |
—
|
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: casino operation | Statement: [Mandalay Resort Group, hadKeyBusinessActivity, casino operation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadKeyBusinessActivity Context triple: [Mandalay Resort Group, hadKeyBusinessActivity, casino operation]
-
A.
hasEntrepreneurialActivity
Indicates that an entity engages in or is associated with starting, managing, or operating business or venture-related activities.
-
B.
hasBusiness
Indicates that one entity owns, operates, or is formally associated with a business entity.
-
C.
hasEconomicActivity
Indicates that an entity engages in, supports, or is associated with a specific type of economic activity or business operation.
-
D.
hasBusinessIn
Indicates that one entity conducts, operates, or maintains business activities within the jurisdiction, location, or domain of another entity.
-
E.
hasKeyBusiness
chosen
Indicates that one entity possesses or is associated with a primary or strategically important business of another entity.
- 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_69f0bd461c208190bec20bbf24e02cc5 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f66c97ee788190a4ef192d3141fa57 |
completed | May 2, 2026, 9:28 p.m. |
| PD | Predicate disambiguation | batch_69f6633ac8a88190ab0cda62bbfcf9b0 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 4:40 p.m.