Triple
T12417302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Norton equivalent circuit |
E296669
|
entity |
| Predicate | symbolForCurrent |
P105000
|
FINISHED |
| Object | IN |
—
|
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: IN | Statement: [Norton equivalent circuit, symbolForCurrent, IN]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: symbolForCurrent Context triple: [Norton equivalent circuit, symbolForCurrent, IN]
-
A.
symbolForState
Indicates that one entity serves as the symbolic representation (such as an icon, emblem, or notation) used to denote or stand for a particular state of another entity.
-
B.
symbolNumber
Indicates a relationship where a specific numerical identifier is assigned to or associated with a particular symbol.
-
C.
symbolElement
Indicates that one entity is a constituent element or component that makes up the other entity, which is treated as a symbol.
-
D.
symbolText
Indicates that a symbol is associated with or represented by a specific piece of text.
-
E.
symbolRoot
Indicates a relationship where one symbol serves as the root or base form from which another symbol is derived or structured.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94e15f21c8190831c9562ffdd4fda |
completed | April 10, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:55 p.m.