Triple
T29057765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC-8801 |
E735435
|
entity |
| Predicate | notableGamePlatformFor |
P122255
|
FINISHED |
| Object | Ys series (early entries) |
E744879
|
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: Ys series (early entries) | Statement: [PC-8801, notableGamePlatformFor, Ys series (early entries)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGamePlatformFor Context triple: [PC-8801, notableGamePlatformFor, Ys series (early entries)]
-
A.
platformsDevelopedFor
Indicates the platforms (e.g., operating systems, devices, or environments) for which something has been specifically created or adapted.
-
B.
appearsInPlatform
chosen
Indicates that an entity is present, available, or featured within a particular platform or system.
-
C.
gamePlatformCategory
Indicates the classification or type of platform on which a game is available or intended to be played.
-
D.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
-
E.
developsOnPlatform
Indicates that one entity is created, built, or developed using the tools, services, or environment provided by another platform 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_69f077e85498819088b65186550da8cd |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a02206665508190ae2324d253ccf377 |
completed | May 11, 2026, 6:31 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a251f7bc5988190b8f64ef8a28777e6 |
completed | June 7, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_6a021fdc6e54819082847bedd97a680b |
completed | May 11, 2026, 6:28 p.m. |
Created at: April 28, 2026, 10:12 a.m.