Triple
T8461729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STD 62 |
E200055
|
entity |
| Predicate | standardTrackStatus |
P82775
|
FINISHED |
| Object | Internet Standards Track |
—
|
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: Internet Standards Track | Statement: [STD 62, standardTrackStatus, Internet Standards Track]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardTrackStatus Context triple: [STD 62, standardTrackStatus, Internet Standards Track]
-
A.
trainingStatus
Indicates the current state or phase of an entity within a training or learning process.
-
B.
statusInSI
Indicates that an entity’s status or condition is specified according to the International System of Units (SI) or an SI-based standard.
-
C.
standardState
Indicates that an entity is in its default, reference, or officially recognized condition or configuration under standard conditions.
-
D.
railStatus
Indicates the current operational condition or state of a rail-related entity (such as a track, line, or service) within the system.
-
E.
statusRecordedBy
Indicates that the status of an entity was documented or captured by a specific agent or system.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe4a0ff4c8190b17bbd33db632cea |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:10 p.m.