Triple
T359898
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edison cylinder phonograph |
E7825
|
entity |
| Predicate | firstDemonstrationDate |
P2570
|
FINISHED |
| Object | 1877-12 |
—
|
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: 1877-12 | Statement: [Edison cylinder phonograph, firstDemonstrationDate, 1877-12]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstDemonstrationDate Context triple: [Edison cylinder phonograph, firstDemonstrationDate, 1877-12]
-
A.
firstDemonstrated
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
-
B.
demonstrationDate
Indicates the date on which a demonstration or protest event takes place or is scheduled to occur.
-
C.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
D.
demonstratedAt
chosen
Indicates that an action, behavior, or capability was shown or exhibited at a particular event, location, or point in time.
-
E.
firstDeployed
Indicates the time or event when something (such as a system, product, or resource) was initially put into active use or operation.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebccb8d88190a31f7c443a0c8566 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95aeed48190b5e48865cc964938 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.