Triple
T36961551
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gathering of Developers |
E914319
|
entity |
| Predicate | notableDeveloperPartner |
P81136
|
FINISHED |
| Object | Remedy Entertainment |
E633956
|
NE 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: Remedy Entertainment | Statement: [Gathering of Developers, notableDeveloperPartner, Remedy Entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDeveloperPartner Context triple: [Gathering of Developers, notableDeveloperPartner, Remedy Entertainment]
-
A.
notablePartner
Indicates that two entities are or have been significant partners, typically in a prominent or noteworthy personal or professional relationship.
-
B.
gameDeveloperPartner
Indicates a partnership relationship where one entity collaborates with another in developing or producing a game.
-
C.
hasNotableDeveloper
chosen
Indicates that an entity has a developer who is particularly prominent, influential, or otherwise notable.
-
D.
technologyPartner
Indicates a collaborative relationship where one entity provides technological expertise, products, or services to support or co-develop another entity’s solutions or operations.
-
E.
majorDeveloper
Indicates that an entity is a primary or leading developer responsible for creating or significantly contributing to another entity.
- F. None of above.
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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3e575664f08190a90714e470dd513a |
completed | June 26, 2026, 10:41 a.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:14 p.m.