Triple
T18227521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester Baby |
E436456
|
entity |
| Predicate | programInputMethod |
P2571
|
FINISHED |
| Object | manual switch entry |
—
|
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: manual switch entry | Statement: [Manchester Baby, programInputMethod, manual switch entry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programInputMethod Context triple: [Manchester Baby, programInputMethod, manual switch entry]
-
A.
inputDevice
chosen
Indicates that one entity functions as a device used to provide input to another entity or system.
-
B.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
C.
input
Indicates that one entity provides data, signals, or resources that are received or processed by another entity.
-
D.
userInterface
Indicates a relationship where one entity serves as the interface or interaction layer through which a user engages with another system, service, or resource.
-
E.
commandInputFormat
Indicates the expected structure or syntax that a command must follow when being provided as input.
- 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_69d8b9103a8081908bbb0836fef10efd |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4f4b0ed5c819096f4fd3a8debc1a4 |
completed | April 19, 2026, 3:28 p.m. |
| PD | Predicate disambiguation | batch_69e4332336cc8190808b9c70c888ba65 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.