Triple
T34345166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IRTF Stream |
E881409
|
entity |
| Predicate | usesSeriesNumbering |
P134912
|
FINISHED |
| Object | global RFC numbering shared with other streams |
—
|
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: global RFC numbering shared with other streams | Statement: [IRTF Stream, usesSeriesNumbering, global RFC numbering shared with other streams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSeriesNumbering Context triple: [IRTF Stream, usesSeriesNumbering, global RFC numbering shared with other streams]
-
A.
hasSeriesNumber
Indicates that an entity is assigned a specific ordinal or sequence number within a series or ordered set.
-
B.
namingSeries
Indicates that one entity serves as the naming convention or series under which another entity is titled or labeled.
-
C.
followsNumbering
chosen
Indicates that one entity adheres to or continues the numbering sequence established by another entity.
-
D.
numberingType
Indicates the scheme or style used to assign sequential numbers or labels within an ordered set.
-
E.
isNumberedBy
Indicates that an entity is assigned, identified, or organized by a specific number or numbering scheme.
- 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_69f349bc55e881908c8e338ef76b0043 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd5bf69acc819092a01e4259785dc3 |
completed | May 8, 2026, 3:43 a.m. |
| PD | Predicate disambiguation | batch_69fd59b3f4ac8190a7f9dd3142da6e09 |
completed | May 8, 2026, 3:34 a.m. |
Created at: May 1, 2026, 1:58 a.m.