Triple
T35562148
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burroughs adding machine |
E1027662
|
entity |
| Predicate | dataEntryMethod |
P183250
|
FINISHED |
| Object | numeric keys |
—
|
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: numeric keys | Statement: [Burroughs adding machine, dataEntryMethod, numeric keys]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataEntryMethod Context triple: [Burroughs adding machine, dataEntryMethod, numeric keys]
-
A.
accessionMethod
Indicates the process or means by which something is acquired, obtained, or added to a collection or system.
-
B.
dataTypeCollected
Indicates that a specific type or category of data is gathered or recorded in the context of an entity or process.
-
C.
dataPortal
Indicates that an entity serves as or is associated with an online interface or gateway through which data can be accessed, managed, or distributed.
-
D.
entrySelectionMethod
Indicates the method or criteria used to select or admit an entity into a particular group, system, or context.
-
E.
filingMethod
Indicates how a document, record, or information is submitted or recorded, such as the process, channel, or format used for filing.
- F. None of above. chosen
Provenance (4 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
| PDg | Predicate description generation | batch_69f79a53ccc481908421ae16e69aa8a4 |
completed | May 3, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:04 p.m.