Triple
T2340403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volta Laboratory |
E45011
|
entity |
| Predicate | locationOfDiscovery |
P3985
|
FINISHED |
| Object | early wax cylinder recording techniques |
—
|
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: early wax cylinder recording techniques | Statement: [Volta Laboratory, locationOfDiscovery, early wax cylinder recording techniques]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationOfDiscovery Context triple: [Volta Laboratory, locationOfDiscovery, early wax cylinder recording techniques]
-
A.
wasDiscoveredIn
Indicates that an entity became known or was first identified during a specific time period or at a particular place.
-
B.
wasDiscoveredAt
chosen
Indicates that an entity was found, identified, or uncovered at a specific place or during a particular event or context.
-
C.
locatedAtTimeOfDiscovery
Indicates the place where something was situated at the moment it was first discovered.
-
D.
discoveryDate
Indicates the date on which something was first discovered or identified.
-
E.
rediscoveredIn
Indicates that something previously known but lost or forgotten was found or identified again at a particular time or place.
- 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_69a88917935081909b755dbf38e81024 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abc6f75d888190a2e41edaa532e83f |
completed | March 7, 2026, 6:34 a.m. |
| PD | Predicate disambiguation | batch_69abc594087c819098100a10c5478a4b |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:52 p.m.