Triple
T18801822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10BASE-T1S |
E459771
|
entity |
| Predicate | lineCoding |
P19896
|
FINISHED |
| Object | PAM3 |
—
|
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: PAM3 | Statement: [10BASE-T1S, lineCoding, PAM3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineCoding Context triple: [10BASE-T1S, lineCoding, PAM3]
-
A.
usesLineCode
chosen
Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
-
B.
lineNumberOrCode
Indicates the specific line number or code identifier associated with an element, reference, or occurrence within a structured sequence or document.
-
C.
codeFor
Indicates that one entity serves as the implementation, encoding, or programmatic representation for another entity.
-
D.
lineNumbering
Indicates that a specific system or document applies sequential numbers to each line of its content.
-
E.
codingUnit
Indicates a relationship where an entity functions as or is associated with a specific unit of code or coding structure.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a02400208190b1d84e2b0640df08 |
completed | April 20, 2026, 3:40 a.m. |
| PD | Predicate disambiguation | batch_69e48d16dd34819096e096d0c0e4c15c |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:53 a.m.