Triple
T19593541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prairie Band Casino & Resort |
E470294
|
entity |
| Predicate | isOwnedByGroup |
P12263
|
FINISHED |
| Object | Native American tribe |
—
|
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: Native American tribe | Statement: [Prairie Band Casino & Resort, isOwnedByGroup, Native American tribe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOwnedByGroup Context triple: [Prairie Band Casino & Resort, isOwnedByGroup, Native American tribe]
-
A.
belongsToGroup
chosen
Indicates that an entity is a member of, or is included within, a particular group or collection.
-
B.
usedByGroup
Indicates that something is utilized or employed by a particular group or collective entity.
-
C.
usesGroup
Indicates that an entity makes use of, operates with, or relies on a particular group as a collective resource, tool, or participant in some activity or process.
-
D.
accessibleForGroups
Indicates that something can be accessed or used by one or more specified groups.
-
E.
hasUserGroup
Indicates that a user is associated with, belongs to, or is a member of a specific user group.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640782e2c8190b5baef07a2bdd015 |
completed | April 20, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:43 p.m.