Triple
T52446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audion vacuum tube |
E1029
|
entity |
| Predicate | filamentFunction |
P2114
|
FINISHED |
| Object | heats cathode |
—
|
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: heats cathode | Statement: [Audion vacuum tube, filamentFunction, heats cathode]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filamentFunction Context triple: [Audion vacuum tube, filamentFunction, heats cathode]
-
A.
envisionedAs
Indicates that one entity is mentally pictured, imagined, or conceived in terms of another entity or role.
-
B.
separatedFunctionFrom
Indicates that one entity has been detached or removed from performing a particular function or role in relation to another entity.
-
C.
material
Indicates that one entity is physically composed of, made from, or constructed using the substance or material represented by the other entity.
-
D.
secondaryFunction
chosen
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
E.
hasLighting
Indicates that one entity is equipped with, contains, or is characterized by a particular type or configuration of lighting.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24c709c248190bcd442c8d508e48c |
completed | Feb. 28, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69a24ac3c8dc819099849023bdaa35a9 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.