Triple
T28617494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Connectix |
E724304
|
entity |
| Predicate | emulationTarget |
P31513
|
FINISHED |
| Object | Sony PlayStation |
—
|
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: Sony PlayStation | Statement: [Connectix, emulationTarget, Sony PlayStation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emulationTarget Context triple: [Connectix, emulationTarget, Sony PlayStation]
-
A.
implementationTarget
Indicates that one entity serves as the concrete implementation or realization of another entity’s specification, interface, or design.
-
B.
emulates
chosen
Indicates that one entity imitates or reproduces the behavior, function, or characteristics of another.
-
C.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
D.
backendTarget
Indicates that one entity serves as the backend system, service, or endpoint that another entity connects to or depends on for processing or functionality.
-
E.
hasSimulator
Indicates that one entity provides or is associated with a simulator used to model, emulate, or test the behavior of another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:32 a.m.