Triple
T29371851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TurboTap |
E744874
|
entity |
| Predicate | inputInterface |
P19412
|
FINISHED |
| Object | TurboGrafx-16 controller plug |
—
|
LITERAL 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: TurboGrafx-16 controller plug | Statement: [TurboTap, inputInterface, TurboGrafx-16 controller plug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputInterface Context triple: [TurboTap, inputInterface, TurboGrafx-16 controller plug]
-
A.
inputAccess
Indicates that one entity has the ability or permission to provide, modify, or otherwise interact with the input of another entity or system.
-
B.
input
chosen
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
C.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
D.
inputIs
Indicates that one entity serves as the input or provided value to another entity, process, or function.
-
E.
inputSpecifier
Indicates a relationship where something defines, constrains, or specifies the form, type, or details of an input used in a process or system.
- 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_69f0a79ba954819094597628112c6091 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 2:27 p.m.