Triple
T34274599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1310 |
E879416
|
entity |
| Predicate | replacedByProcessDefinedIn |
P195246
|
FINISHED |
| Object | RFC 2026 |
—
|
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 2026 | Statement: [RFC 1310, replacedByProcessDefinedIn, RFC 2026]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByProcessDefinedIn Context triple: [RFC 1310, replacedByProcessDefinedIn, RFC 2026]
-
A.
replacedProcess
Indicates that one process has been substituted or superseded by another process.
-
B.
replacedByRule
Indicates that an entity has been superseded or substituted by another entity according to a specific rule or transformation.
-
C.
replacedByInProduction
Indicates that one entity has been superseded and is no longer used in production because another specified entity has taken its place.
-
D.
modifiedByProcess
Indicates that an entity has been changed or altered as a result of a specific process.
-
E.
definesProcessFor
Indicates that one entity specifies or establishes the process or procedure to be used for another entity.
- F. None of above. chosen
Provenance (4 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_69f349b5f6648190b9420d94a4cd16e0 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
| PDg | Predicate description generation | batch_69fdb3172b808190b590d7c5be31ebb7 |
completed | May 8, 2026, 9:55 a.m. |
Created at: May 1, 2026, 1:56 a.m.