Triple
T36957215
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unreal |
E914217
|
entity |
| Predicate | expansionPublisher |
P187451
|
FINISHED |
| Object | GT Interactive |
—
|
NE NERFINISHED |
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: GT Interactive | Statement: [Unreal, expansionPublisher, GT Interactive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expansionPublisher Context triple: [Unreal, expansionPublisher, GT Interactive]
-
A.
expansionDeveloper
Indicates that an entity is responsible for creating, extending, or enhancing the expansion of another entity (such as a product, system, or project).
-
B.
expansionAdded
Indicates that an additional component, feature, or content has been incorporated into an existing entity or system.
-
C.
expands
Indicates that one entity increases in size, volume, scope, or extent relative to a previous state or another entity.
-
D.
expansionSystem
Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
-
E.
expansionPartner
Indicates a relationship where one entity collaborates with another to support or drive its growth into new markets, regions, or domains.
- F. None of above. chosen
Provenance (4 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: May 3, 2026, 4:13 p.m.