Triple
T34082568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCP 12 |
E874083
|
entity |
| Predicate | givesRecommendationsOn |
P5662
|
FINISHED |
| Object | technical content of RFC 1908 |
—
|
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: technical content of RFC 1908 | Statement: [BCP 12, givesRecommendationsOn, technical content of RFC 1908]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesRecommendationsOn Context triple: [BCP 12, givesRecommendationsOn, technical content of RFC 1908]
-
A.
canRecommend
Indicates that one entity is able or authorized to suggest or endorse another entity as suitable or preferable.
-
B.
recommendation
chosen
Indicates that one entity suggests, endorses, or advises another entity as suitable or beneficial for a particular purpose or context.
-
C.
commendationType
Indicates the specific category or kind of commendation associated with an action or relationship.
-
D.
madeRecommendation
Indicates that one entity has suggested or advised another entity to consider a particular option, action, or choice.
-
E.
commendedFor
Indicates that one entity has expressed praise or approval toward another entity specifically because of a particular action, quality, or achievement.
- 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_69f349a61d448190b74642f325d3eb7a |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f70c07bed48190976f4405d4a3d642 |
completed | May 3, 2026, 8:49 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:52 a.m.