Triple
T31948053
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Network Time Security |
E815704
|
entity |
| Predicate | abbreviationOfProtectedProtocol |
P36183
|
FINISHED |
| Object | NTP |
—
|
NE NERFINISHED |
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: NTP | Statement: [Network Time Security, abbreviationOfProtectedProtocol, NTP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbreviationOfProtectedProtocol Context triple: [Network Time Security, abbreviationOfProtectedProtocol, NTP]
-
A.
abbreviationOfThirdParty
Indicates that one term is an abbreviation or shortened form of a name or phrase that belongs to or is used by a third party.
-
B.
abbreviationOfAccessType
Indicates that one access type is an abbreviation or shortened form of another access type.
-
C.
encryptionProtocol
Indicates that one entity uses, specifies, or is governed by a particular method or standard for encrypting data in its communications or storage.
-
D.
associatedProtocol
Indicates that one entity is linked to, governed by, or operates according to a particular protocol.
-
E.
abbreviationUsedFor
chosen
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 12:07 a.m.