Triple
T5264276
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AirPods Max |
E118901
|
entity |
| Predicate | connectionPort |
P62623
|
FINISHED |
| Object | Lightning |
—
|
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: Lightning | Statement: [AirPods Max, connectionPort, Lightning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectionPort Context triple: [AirPods Max, connectionPort, Lightning]
-
A.
registeredPort
Indicates that a specific network port number has been officially assigned and recorded for use by a particular service or protocol.
-
B.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
C.
controlledPort
Indicates that one entity has authority over or manages the operation or configuration of a specific port of another entity.
-
D.
terminusPort
Indicates the port at which a route, journey, or connection ends or terminates.
-
E.
registryPort
Indicates the network port number on which a registry service is exposed or accessed.
- 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_69bd446a42c88190b7ecbef006561d55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bd4a9888190a79ef8e64c764f86 |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:51 p.m.