Triple
T27672082
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NX-API |
E697688
|
entity |
| Predicate | transportSecurity |
P104463
|
FINISHED |
| Object | TLS |
—
|
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: TLS | Statement: [NX-API, transportSecurity, TLS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportSecurity Context triple: [NX-API, transportSecurity, TLS]
-
A.
supportsEncryptionInTransit
chosen
Indicates that one entity provides or enables protection of data while it is being transmitted between entities.
-
B.
transportProtocol
Indicates the communication protocol used to transport data between entities in a networked interaction.
-
C.
securesProtocol
Indicates that one entity protects, safeguards, or enforces the security of a communication or operational protocol for another entity.
-
D.
securedVia
Indicates that something is protected, authenticated, or made safe through a specified method, mechanism, or channel.
-
E.
transportPolicy
Indicates a relationship where an authority or organization defines rules, strategies, or guidelines governing how transportation systems are planned, operated, or regulated.
- 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_69ef590d458c81909583290c3cd0478b |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 2:41 p.m.