Triple
T32516607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5639 |
E831076
|
entity |
| Predicate | specifiesForUseIn |
P66302
|
FINISHED |
| Object | cryptographic applications |
—
|
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: cryptographic applications | Statement: [RFC 5639, specifiesForUseIn, cryptographic applications]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesForUseIn Context triple: [RFC 5639, specifiesForUseIn, cryptographic applications]
-
A.
specifiedFor
chosen
Indicates that something is designated or intended to be used for a particular entity, purpose, or context.
-
B.
usedToSpecify
Indicates that one entity is employed to define, clarify, or determine the characteristics or identity of another entity.
-
C.
isIntendedForUseBy
Indicates that something is designed, meant, or purposed to be used by a particular entity or group.
-
D.
assessesForUseIn
Indicates that one entity evaluates another entity to determine its suitability or appropriateness for a particular use or application.
-
E.
usedFor
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 1, 2026, 1 a.m.