Triple
T19234752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GMII |
E480963
|
entity |
| Predicate | collisionSignalsUsedFor |
P135291
|
FINISHED |
| Object | half-duplex compatibility |
—
|
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: half-duplex compatibility | Statement: [GMII, collisionSignalsUsedFor, half-duplex compatibility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collisionSignalsUsedFor Context triple: [GMII, collisionSignalsUsedFor, half-duplex compatibility]
-
A.
colliderUsed
Indicates that a particular collider or collision-detection component is employed or involved in an interaction or event between entities.
-
B.
collisionSystem
Indicates a physical interaction where two or more entities impact or collide with each other within a defined system or environment.
-
C.
collisionDetectionMethod
Indicates the technique or algorithm used to determine whether two or more entities come into contact or intersect.
-
D.
marksCollisionBetween
Indicates a recorded event or state where two or more entities have come into contact or collided with each other.
-
E.
collisionDomain
Indicates that two or more network entities share the same collision domain, meaning their transmissions can interfere and cause packet collisions with each other.
- 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_69d8e8ccb8f48190ad420098e74fb1db |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5faeb53988190b83afee9974058c6 |
completed | April 20, 2026, 10:07 a.m. |
| PD | Predicate disambiguation | batch_69e4dcfae6f081909cc173cf71a5005c |
completed | April 19, 2026, 1:47 p.m. |
| PDg | Predicate description generation | batch_69e4debc39ac81908b7c5ef797046360 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 1:26 p.m.