Triple
T21190933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1883 |
E522208
|
entity |
| Predicate | specifiesField |
P33246
|
FINISHED |
| Object | IPv6 Version field |
—
|
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: IPv6 Version field | Statement: [RFC 1883, specifiesField, IPv6 Version field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesField Context triple: [RFC 1883, specifiesField, IPv6 Version field]
-
A.
definesField
chosen
Indicates that one entity specifies or declares a particular field or attribute that belongs to or characterizes another entity.
-
B.
definedInField
Indicates that something (such as a concept, method, or element) is formally specified, declared, or established within a particular field, domain, or area of study.
-
C.
supportsField
Indicates that one entity provides the necessary structure, stability, or backing for a particular field, area, or domain associated with another entity.
-
D.
specifiedFor
Indicates that something is designated or intended to be used for a particular entity, purpose, or context.
-
E.
recognisesField
Indicates that one entity acknowledges, identifies, or accepts a particular field (such as an area of study, expertise, or data attribute) as valid or relevant.
- 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_69e0b51061388190aa03f19700d3ef04 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e733372b488190920174955b4b9172 |
completed | April 21, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69e5f6027c248190a170a36612bd337e |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:07 p.m.