Triple
T29340541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PC-98 |
E744023
|
entity |
| Predicate | hasEmulationSupportIn |
P31906
|
FINISHED |
| Object | Neko Project II |
—
|
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: Neko Project II | Statement: [PC-98, hasEmulationSupportIn, Neko Project II]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEmulationSupportIn Context triple: [PC-98, hasEmulationSupportIn, Neko Project II]
-
A.
hasSimulator
chosen
Indicates that one entity provides or is associated with a simulator used to model, emulate, or test the behavior of another entity.
-
B.
hasFeature
Indicates that an entity possesses, exhibits, or includes a particular characteristic, attribute, or component.
-
C.
supportsHardwareAcceleration
Indicates that one entity enables or provides hardware-based acceleration capabilities for another entity’s operations or processes.
-
D.
hasCompatibilityMode
Indicates that one entity operates under a special mode or setting designed to maintain compatibility with another entity or with an earlier version.
-
E.
hasSupported
Indicates that one entity has provided assistance, endorsement, or backing to another entity, either materially, emotionally, or through advocacy.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f669261f588190aa20417cfee752e4 |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 1:33 p.m.