Triple
T34046619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Electroencephalography |
E873101
|
entity |
| Predicate | firstHumanEEGRecordedInYear |
P14790
|
FINISHED |
| Object | 1924 |
—
|
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: 1924 | Statement: [Electroencephalography, firstHumanEEGRecordedInYear, 1924]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstHumanEEGRecordedInYear Context triple: [Electroencephalography, firstHumanEEGRecordedInYear, 1924]
-
A.
firstRecordedWith
Indicates that an entity’s earliest known or documented occurrence is associated with a specified context, source, or accompanying entity.
-
B.
firstRecordingDate
Indicates the date on which an entity’s first recording (e.g., audio, video, or similar captured performance) was made.
-
C.
firstRadioReadingYear
Indicates the year in which an entity’s radio reading or broadcast was first recorded or took place.
-
D.
firstReportedYear
chosen
Indicates the year in which something was initially reported, documented, or made known for the first time.
-
E.
firstPublicUseYear
Indicates the calendar year in which something was first made available for use by the public.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379f963908190846d232f386fd98f |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:51 a.m.