Triple
T31947901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 9589 |
E815700
|
entity |
| Predicate | abbrev |
P99168
|
FINISHED |
| Object | RFC 9589 |
—
|
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: RFC 9589 | Statement: [RFC 9589, abbrev, RFC 9589]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abbrev Context triple: [RFC 9589, abbrev, RFC 9589]
-
A.
abbreviation
Indicates that one term is a shortened or contracted form that stands for another, longer expression.
-
B.
abbreviationOrShortForm
chosen
Indicates that one term is an abbreviation or shortened form of another term.
-
C.
abbreviationUsedBy
Indicates that a particular abbreviation is employed or adopted by a specified entity in its communication, documentation, or usage.
-
D.
abbreviationUsedFor
Indicates that a particular shortened form or acronym is used to represent or stand in for a longer term, name, or expression.
-
E.
abbreviationScript
Indicates that one entity is an abbreviated form of another entity written in a specific script or writing system.
- 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_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 12:07 a.m.