Triple
T13686523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 0960 |
E328142
|
entity |
| Predicate | standardizationPhase |
P8040
|
FINISHED |
| Object | early Internet standard |
—
|
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: early Internet standard | Statement: [RFC 0960, standardizationPhase, early Internet standard]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardizationPhase Context triple: [RFC 0960, standardizationPhase, early Internet standard]
-
A.
standardizationStatus
chosen
Indicates the current stage or condition of an entity in a formal standardization process (e.g., proposed, under review, approved, deprecated).
-
B.
laterStandardization
Indicates that one entity becomes standardized or formally established at a later time than another entity.
-
C.
standardizationApproach
Indicates the method or strategy used to establish, implement, or align with a common standard across entities or processes.
-
D.
standardizationGoal
Indicates the intended level, outcome, or target state to be achieved through a process of standardization.
-
E.
timePeriodOfStandardization
Indicates the time span during which a particular standard was formally established or in effect.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc670968881908e2b4fdf656c7285 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.