Triple
T12829354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BL-5C battery |
E306742
|
entity |
| Predicate | hasTerminals |
P107095
|
FINISHED |
| Object | positive terminal |
—
|
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: positive terminal | Statement: [BL-5C battery, hasTerminals, positive terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTerminals Context triple: [BL-5C battery, hasTerminals, positive terminal]
-
A.
hasSubTerminal
Indicates that an entity includes or is associated with a subordinate or lower-level terminal element within a hierarchical structure.
-
B.
hasTerminalFunction
Indicates that something possesses a function or role specifically associated with an endpoint, boundary, or final stage within a system or process.
-
C.
hasTerminusIn
Indicates that something (such as a route, line, or path) ends or has its final stopping point at a specified location.
-
D.
hasLeaves
Indicates that an entity possesses leaves as part of its structure or form.
-
E.
isTerminal
Indicates that an entity represents an endpoint or final state in a process, structure, or sequence, with no further continuation beyond it.
- 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_69d7bdf52b94819096d6f0ba4ab50a98 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9714208f881908f7f8a921362909a |
completed | April 10, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69d96fa08cd481909a946046ba63809f |
completed | April 10, 2026, 9:46 p.m. |
| PDg | Predicate description generation | batch_69d9713e45a88190acd346f066093550 |
completed | April 10, 2026, 9:53 p.m. |
Created at: April 9, 2026, 5:34 p.m.