Triple
T28618673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFB protocol |
E724328
|
entity |
| Predicate | supportsSecurityType |
P3487
|
FINISHED |
| Object | None |
—
|
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: None | Statement: [RFB protocol, supportsSecurityType, None]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsSecurityType Context triple: [RFB protocol, supportsSecurityType, None]
-
A.
hasSecuritySupport
Indicates that one entity provides security-related assistance, maintenance, or protection services for another entity.
-
B.
securityType
chosen
Indicates the classification or category of security associated with an entity, such as the type of financial instrument, protection mechanism, or access control applied.
-
C.
securityTypeListed
Indicates that a security is officially listed and traded on a recognized exchange or trading venue.
-
D.
securityTypePermitted
Indicates that a particular type or category of security is allowed or authorized within a given context or system.
-
E.
hasSecurityStandard
Indicates that an entity complies with, follows, or is governed by a specified security standard or framework.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_6a017e7bdfe481909cb4d5bdede6035e |
completed | May 11, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_6a017defee108190bdf5f98dc415b250 |
completed | May 11, 2026, 6:57 a.m. |
Created at: April 28, 2026, 4:32 a.m.