Triple
T38308271
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cat 5e |
E1033613
|
entity |
| Predicate | commonConnector |
P55011
|
FINISHED |
| Object | RJ45 |
—
|
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: RJ45 | Statement: [Cat 5e, commonConnector, RJ45]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonConnector Context triple: [Cat 5e, commonConnector, RJ45]
-
A.
commonConnectorName
chosen
Indicates that two or more entities share the same connector name used to link or interface them.
-
B.
connectionStandard
Indicates the technical standard or protocol that defines how a connection between entities is established and operates.
-
C.
connectsWorks
Indicates a relationship where one work serves to link, bridge, or associate two or more other works.
-
D.
connectorType
Indicates the specific kind or category of connection interface that links two entities.
-
E.
connectsBeyond
Indicates a relationship where one entity forms a link or association that extends past a usual boundary, scope, or intermediary to reach 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_69f76e132c408190969b3d35c04b87ae |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:30 p.m.