Triple
T28212511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maverick franchise |
E711211
|
entity |
| Predicate | knownForElement |
P111120
|
FINISHED |
| Object | poker games |
—
|
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: poker games | Statement: [Maverick franchise, knownForElement, poker games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForElement Context triple: [Maverick franchise, knownForElement, poker games]
-
A.
knowsAs
Indicates that one entity recognizes or refers to another entity by a particular name, alias, or identifier.
-
B.
knownForPosition
Indicates that an entity is notably recognized or distinguished for holding a particular position, role, or office.
-
C.
knownIn
Indicates that an entity is recognized, acknowledged, or familiar within a particular context, domain, or group.
-
D.
namedForKnownFor
Indicates that one entity is named after another entity specifically because that other entity is notable or recognized for something.
-
E.
referentKnownFor
chosen
Indicates that the referent is widely recognized or notable for a particular activity, role, achievement, or characteristic.
- 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_69efb51cb5288190818c1f63a266af11 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 27, 2026, 10:40 p.m.