Triple
T11880020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MGM Cotai |
E282629
|
entity |
| Predicate | hasCasinoLicense |
P12714
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [MGM Cotai, hasCasinoLicense, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCasinoLicense Context triple: [MGM Cotai, hasCasinoLicense, yes]
-
A.
hasCasino
Indicates that an entity includes, contains, or is associated with a casino facility or gambling establishment.
-
B.
gamingLicenseIssuer
Indicates the authority or entity that grants or issues a gaming license to another party.
-
C.
hasGamingLicenseJurisdiction
Indicates that an entity holds legal authority or permission to conduct gaming activities within a specified jurisdiction.
-
D.
hasLicense
chosen
Indicates that an entity possesses a valid authorization or permit, typically granted by an authority, to perform a specific activity or use something.
-
E.
majorCasinoOperatorPresence
Indicates that a major casino operator has an established operational or business presence in relation to the referenced entity or location.
- 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_69d6ab2945d081908a5851c916cbcfb5 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8d39d2934819093b9f7006f45e5cb |
completed | April 10, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69d8bb272f88819090c37c944c5a60ab |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:44 p.m.