Triple
T4370891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100BASE-X |
E98892
|
entity |
| Predicate | usesLineCoding |
P19896
|
FINISHED |
| Object | 4B/5B |
—
|
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: 4B/5B | Statement: [100BASE-X, usesLineCoding, 4B/5B]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesLineCoding Context triple: [100BASE-X, usesLineCoding, 4B/5B]
-
A.
usesLineCode
chosen
Indicates that one entity employs or references a specific line code as part of its operation, identification, or communication.
-
B.
usesLineCharacteristic
Indicates that one entity employs or is based on a specific characteristic or property of a line.
-
C.
usesLineFolding
Indicates that an entity applies line folding, breaking long lines into shorter ones according to specific rules or constraints.
-
D.
isLinedWith
Indicates that one object or surface is covered, edged, or internally coated along its length or area with another material or layer.
-
E.
lineUses
Indicates that a particular line (such as a route, service, or connection) makes use of or is implemented using a specified resource, infrastructure, or element.
- 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_69b3454db3708190aeafd814413c4c3d |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3521cb7ec8190b7b79675871d97d8 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:17 p.m.