Triple
T34082579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BCP 57 |
E874084
|
entity |
| Predicate | updatesGuidanceFrom |
P132457
|
FINISHED |
| Object | RFC 1908 |
—
|
NE NERFINISHED |
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 1908 | Statement: [BCP 57, updatesGuidanceFrom, RFC 1908]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatesGuidanceFrom Context triple: [BCP 57, updatesGuidanceFrom, RFC 1908]
-
A.
revisedGuidelinesIssued
Indicates that updated or modified guidelines have been formally created and released by an authority or governing body.
-
B.
updatesFrom
chosen
Indicates that one entity is revised, modified, or brought to a newer state based on information, changes, or content originating from another entity.
-
C.
updated
Indicates that an entity has been modified or brought to a more recent state compared to its previous version or status.
-
D.
providesGuidanceTo
Indicates that one entity offers direction, advice, or instruction to another entity.
-
E.
updatesPracticeFor
Indicates that one entity revises or modifies a practice, procedure, or method on behalf of or in relation to another entity.
- 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.