Triple
T7921492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nernst–Lamp |
E183953
|
entity |
| Predicate | typicalApplicationEra |
P3656
|
FINISHED |
| Object | early 20th century |
—
|
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 20th century | Statement: [Nernst–Lamp, typicalApplicationEra, early 20th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalApplicationEra Context triple: [Nernst–Lamp, typicalApplicationEra, early 20th century]
-
A.
notablePlatformEra
Indicates that an entity is notably associated with a particular platform during a specific era or period of prominence.
-
B.
appliesToEra
Indicates that something is relevant, valid, or in effect during a particular historical or temporal era.
-
C.
targetAudienceEra
Indicates the historical period or era for which something (such as a work, product, or message) is primarily intended or designed as its audience.
-
D.
discoveryEra
Indicates the historical period or era during which the entity was discovered or first identified.
-
E.
historicalPeriodOfUse
chosen
Indicates the time period during which something was in active use or commonly utilized.
- 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_69ca828efbe48190bd48482650182e79 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a9499cc8190b6bd81f4625c77ab |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9316e98819080be7bf1a6ff92f1 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:06 p.m.