Triple
T6833337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | i |
E157389
|
entity |
| Predicate | alternativeNotation |
P57346
|
FINISHED |
| Object | j (in electrical engineering) |
—
|
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: j (in electrical engineering) | Statement: [i, alternativeNotation, j (in electrical engineering)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternativeNotation Context triple: [i, alternativeNotation, j (in electrical engineering)]
-
A.
hasAlternativeNotation
chosen
Indicates that an entity can be represented or written in a different, equivalent form or notation.
-
B.
informalNotation
Indicates that an entity is represented or expressed using a non-standard, simplified, or colloquial form of notation rather than a formal or fully rigorous one.
-
C.
notation
Indicates a conventional way of symbolically representing or writing something, such as concepts, quantities, or operations, within a specific system.
-
D.
distinguishingNotation
Indicates that one entity uses a specific notation or symbol to distinguish or differentiate another entity from similar ones.
-
E.
alternativeForm
Indicates that one entity is an alternative version, variant, or representation of another entity.
- 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_69c6882c53608190b99aebef079b23bd |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d62b1e8c8190a81d91191a54b073 |
completed | March 27, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69c6d09d95f0819091ca7f897dc21efe |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:18 p.m.