Triple
T52443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Audion vacuum tube |
E1029
|
entity |
| Predicate | cathodeFunction |
P3265
|
FINISHED |
| Object | emits electrons when heated |
—
|
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: emits electrons when heated | Statement: [Audion vacuum tube, cathodeFunction, emits electrons when heated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cathodeFunction Context triple: [Audion vacuum tube, cathodeFunction, emits electrons when heated]
-
A.
secondaryFunction
Indicates that an entity has an additional, supporting role or purpose beyond its primary function.
-
B.
hasPrimaryFunction
Indicates that one entity serves as the main or principal function or role of another entity.
-
C.
cableType
Indicates the specific kind or category of cable associated with or used by an entity.
-
D.
fueledBy
Indicates that one entity provides the energy or power source that enables the operation or functioning of another entity.
-
E.
separatedFunctionFrom
Indicates that one entity has been detached or removed from performing a particular function or role in relation to another entity.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69a24c6ff0588190b0fd864da9aa8569 |
completed | Feb. 28, 2026, 2:01 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.