Triple
T2874393
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Power Mac G5 |
E56840
|
entity |
| Predicate | frontPorts |
P1763
|
FINISHED |
| Object | USB 2.0 |
—
|
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: USB 2.0 | Statement: [Power Mac G5, frontPorts, USB 2.0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frontPorts Context triple: [Power Mac G5, frontPorts, USB 2.0]
-
A.
portAlsoKnownAs
Indicates that a port is referred to by an alternative name or alias.
-
B.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
C.
openedPort
Indicates that a network port on a host or device is currently open and able to accept incoming connections.
-
D.
port
chosen
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
-
E.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
- 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_69ab4a4ced288190ab6d3e062d10f7f6 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abe0032ddc8190bb4d15ec7e3c63e8 |
completed | March 7, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69abdd142e4c8190b424cb0c5ff40d04 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:03 p.m.