Triple
T1718344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFS |
E37337
|
entity |
| Predicate | authenticationMechanism |
P18412
|
FINISHED |
| Object | AUTH_SYS |
—
|
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: AUTH_SYS | Statement: [NFS, authenticationMechanism, AUTH_SYS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authenticationMechanism Context triple: [NFS, authenticationMechanism, AUTH_SYS]
-
A.
authenticationType
chosen
Indicates the method or mechanism used to verify and confirm an entity’s identity in an interaction or system.
-
B.
authenticationStandard
Indicates that one entity defines, specifies, or adheres to a particular method, protocol, or set of rules for verifying the identity of another entity.
-
C.
securityMechanism
Indicates a relationship where one entity serves as a means or method to protect another entity from threats, vulnerabilities, or unauthorized actions.
-
D.
authenticationRequired
Indicates that access to a resource or operation is restricted and can only be performed by entities that have successfully authenticated.
-
E.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
- 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_69a8861912dc8190931af43b4b9158a7 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69ab5c96db6c8190a745d6fef7bf2cdb |
completed | March 6, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69aa61bed2fc819086d912cd34285978 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:30 p.m.