Triple
T36663883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Micro-A |
E905204
|
entity |
| Predicate | groundPin |
P82795
|
FINISHED |
| Object | GND |
—
|
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: GND | Statement: [USB Micro-A, groundPin, GND]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: groundPin Context triple: [USB Micro-A, groundPin, GND]
-
A.
ground
Indicates that one entity is in contact with or supported by the ground or a ground-like surface.
-
B.
groundComponent
Indicates that one entity serves as a foundational or base part upon which another entity is built, attached, or functionally dependent.
-
C.
groundService
Indicates that one entity provides ground-based operational support or services to another entity, typically in a transportation or logistics context.
-
D.
groundServiceFeature
Indicates a relationship where a ground service provides or includes a particular feature or amenity.
-
E.
signalGroundPins
chosen
Indicates that certain pins serve as ground reference connections for signal-carrying pins in an electrical or electronic interface.
- 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.