Triple
T19398452
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tesla solar inverter |
E485252
|
entity |
| Predicate | inputCurrentType |
P11909
|
FINISHED |
| Object | DC |
—
|
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: DC | Statement: [Tesla solar inverter, inputCurrentType, DC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inputCurrentType Context triple: [Tesla solar inverter, inputCurrentType, DC]
-
A.
inputType
chosen
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
B.
hasCurrentType
Indicates that an entity currently possesses or is classified under a specific type or category, as opposed to past or potential types.
-
C.
inputIs
Indicates that one entity serves as the input or provided value to another entity, process, or function.
-
D.
currentTractionType
Indicates the type or mode of traction currently being applied or in use in a given context.
-
E.
inputSpecifier
Indicates a relationship where something defines, constrains, or specifies the form, type, or details of an input used in a process or system.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62574edd08190b5456108d5e3907e |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.