Triple
T5064694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3bz |
E114113
|
entity |
| Predicate | supportsReach |
P61051
|
FINISHED |
| Object | up to 100 meters on suitable cabling |
—
|
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: up to 100 meters on suitable cabling | Statement: [IEEE 802.3bz, supportsReach, up to 100 meters on suitable cabling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsReach Context triple: [IEEE 802.3bz, supportsReach, up to 100 meters on suitable cabling]
-
A.
supportedAct
Indicates that one entity provided assistance, endorsement, or backing for a particular action or activity performed by another entity.
-
B.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
C.
supportsUse
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
D.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
E.
supportsReferral
Indicates that one entity enables, accepts, or facilitates referrals being made to another entity or service.
- 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_69bd443c0c8c81908663b77afb28e165 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7478f7988190bc0473e8af055147 |
completed | March 20, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69bd715622b48190a3e8e49a5ef62b4a |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd738ac2e0819099c06cdcc5e21d28 |
completed | March 20, 2026, 4:19 p.m. |
Created at: March 20, 2026, 1:38 p.m.