Triple
T17022986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JOHNNIAC |
E412990
|
entity |
| Predicate | programmingInputMethod |
P95862
|
FINISHED |
| Object | plugboard and punched cards |
—
|
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: plugboard and punched cards | Statement: [JOHNNIAC, programmingInputMethod, plugboard and punched cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmingInputMethod Context triple: [JOHNNIAC, programmingInputMethod, plugboard and punched cards]
-
A.
cangjieInput
Indicates the mapping from a character to its corresponding Cangjie input code used for text entry.
-
B.
hasTypingFeature
chosen
Indicates that an entity possesses or supports a particular typing-related characteristic or capability.
-
C.
keyboardFeature
Indicates that one entity is a feature, characteristic, or functional attribute of a keyboard.
-
D.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
E.
keyHitter
Indicates that an entity is a powerful or highly effective performer, especially in a competitive or performance-based context.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d2abbc81908943becf5f539fc6 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.