Triple
T36663838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USB Mini-A |
E905203
|
entity |
| Predicate | dataLines |
P152594
|
FINISHED |
| Object | D+ and D- |
—
|
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: D+ and D- | Statement: [USB Mini-A, dataLines, D+ and D-]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataLines Context triple: [USB Mini-A, dataLines, D+ and D-]
-
A.
hasLines
chosen
Indicates that one entity contains, is composed of, or is associated with one or more linear elements or line segments.
-
B.
definedLine
Indicates that a specific line (such as a boundary, path, or reference line) has been formally established or specified within a given context.
-
C.
damLine
Indicates that one entity is the maternal lineage or female ancestral line from which the other entity descends.
-
D.
fastLinesUsedBy
Indicates that certain fast transportation or communication lines are utilized by a particular entity.
-
E.
testingLine
Indicates that one entity is being used as a test or trial version of a line, sequence, or boundary associated with 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_69f76e6e3b908190970251b30f76ad71 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c77ef4108190aa83a9f595e34905 |
completed | May 3, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.