Triple
T806622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Folded-port InfraRed Echellette |
E17450
|
entity |
| Predicate | portConfiguration |
P21260
|
FINISHED |
| Object | folded port |
—
|
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: folded port | Statement: [Folded-port InfraRed Echellette, portConfiguration, folded port]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: portConfiguration Context triple: [Folded-port InfraRed Echellette, portConfiguration, folded port]
-
A.
portNumber
Indicates the specific communication port assigned to a network connection, service, or endpoint.
-
B.
port
Indicates a relationship where one entity serves as a harbor, access point, or interface through which another entity can enter, exit, or connect.
-
C.
portFunction
Indicates the specific operational role or purpose that a port serves within a system or network.
-
D.
typicalPort
Indicates that a specified port is commonly or normally used for a given service, protocol, or application.
-
E.
portRange
Indicates the range of network ports over which a connection, service, or rule applies.
- 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_69a4937ae8a08190b5084a03d532b30e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ac07fedc8190ab05595f25c1792f |
completed | March 1, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69a4aa7221c081908068e66fe720f26d |
completed | March 1, 2026, 9:06 p.m. |
| PDg | Predicate description generation | batch_69a4ac0688708190b62ac0a8239ec8c8 |
completed | March 1, 2026, 9:13 p.m. |
Created at: March 1, 2026, 7:38 p.m.