Triple
T33536639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Tetris Company |
E858952
|
entity |
| Predicate | hasOfficialPortalFor |
P2274
|
FINISHED |
| Object | Tetris 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: Tetris games | Statement: [The Tetris Company, hasOfficialPortalFor, Tetris games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOfficialPortalFor Context triple: [The Tetris Company, hasOfficialPortalFor, Tetris games]
-
A.
isOfficialPortalFor
chosen
Indicates that one entity serves as the recognized, authoritative portal or entry point for accessing information or services related to another entity.
-
B.
hasPortal
Indicates that one entity possesses or provides access to a portal connecting to another location or entity.
-
C.
hasOfficialWebsiteThrough
Indicates that an entity has an official website that is accessed, provided, or mediated via a specified intermediary, platform, or channel.
-
D.
hasMainPortal
Indicates that one entity serves as the primary or main portal (entry point or access interface) for another entity.
-
E.
hasOfficial
Indicates that an entity is formally associated with, represented by, or served by a designated official or office-holder.
- 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_69f34978caf4819083f90eba4944d8e8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:39 a.m.