Triple
T31968478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 5907 |
E816243
|
entity |
| Predicate | definesForVersion |
P87767
|
FINISHED |
| Object | NTP version 4 |
—
|
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: NTP version 4 | Statement: [RFC 5907, definesForVersion, NTP version 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesForVersion Context triple: [RFC 5907, definesForVersion, NTP version 4]
-
A.
definesVersionOf
chosen
Indicates that one entity specifies or establishes the version or variant identity of another entity.
-
B.
introducedVersionOf
Indicates that one entity is the version in which another entity was first introduced or made available.
-
C.
introducedWithVersion
Indicates that something first became available or was added starting from a specific version.
-
D.
hasVersionFor
Indicates that one entity serves as a specific version or variant tailored for another entity.
-
E.
supportsSinceVersion
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
- 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_69f348f5ae5481909da0247869f51955 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd91a5dad8819093eeeef527027890 |
completed | May 8, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69fd8f65fe9081908902500a3228d935 |
completed | May 8, 2026, 7:23 a.m. |
Created at: May 1, 2026, 12:10 a.m.