Triple
T20375304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit Partnership |
E497675
|
entity |
| Predicate | primaryRevenueSources |
P13615
|
FINISHED |
| Object | gambling operations |
—
|
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: gambling operations | Statement: [Detroit Partnership, primaryRevenueSources, gambling operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRevenueSources Context triple: [Detroit Partnership, primaryRevenueSources, gambling operations]
-
A.
revenueSources
chosen
Indicates the relationship identifying where an entity’s revenue comes from or the different streams that generate its income.
-
B.
majorRevenueSource
Indicates that one entity serves as the primary or dominant source of revenue for another entity.
-
C.
revenue
Indicates the amount of income generated by an entity from its business activities or operations over a specified period.
-
D.
revenueUse
Indicates how generated revenue is allocated, spent, or applied toward specific purposes or activities.
-
E.
revenueSourceShift
Indicates a change in where or how an entity primarily generates its revenue, such as moving from one main income stream or business model to another.
- 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_69e0b4a5b7908190a972e4e7e698ae94 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e678acae3c8190ae04323760bf5597 |
completed | April 20, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e57648be3c81908256838228cabf5c |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:27 a.m.