Triple
T5437411
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Computers and Tabulators |
E122042
|
entity |
| Predicate | dataInputMethod |
P11909
|
FINISHED |
| Object | 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: punched cards | Statement: [International Computers and Tabulators, dataInputMethod, punched cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataInputMethod Context triple: [International Computers and Tabulators, dataInputMethod, punched cards]
-
A.
inputDevice
Indicates that one entity functions as a device used to provide input to another entity or system.
-
B.
inputType
chosen
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.
hasKeyboard
Indicates that one entity possesses or is equipped with a keyboard as a component or accessory.
-
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_69bd46400768819092925d461c0b8432 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd922f66bc8190b7d47fd68d2fcf2e |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd919aeb048190b786f814177d6cd9 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:07 p.m.