Triple
T1611122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tom Preston-Werner |
E34614
|
entity |
| Predicate | notablePublication |
P4
|
FINISHED |
| Object | Semantic Versioning 2.0.0 specification |
E183286
|
NE 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: Semantic Versioning 2.0.0 specification | Statement: [Tom Preston-Werner, notablePublication, Semantic Versioning 2.0.0 specification]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Semantic Versioning 2.0.0 specification Context triple: [Tom Preston-Werner, notablePublication, Semantic Versioning 2.0.0 specification]
-
A.
Semantic Versioning specification
chosen
The Semantic Versioning specification is a widely adopted versioning scheme for software that defines clear rules for incrementing version numbers based on backward-incompatible changes, new features, and bug fixes.
-
B.
RFC 8174
RFC 8174 is an IETF document that clarifies the interpretation of requirement-level keywords like “MUST” and “SHOULD” in technical specifications, updating the guidance originally given in RFC 2119.
-
C.
RFC 6020
RFC 6020 is the IETF specification that defines the YANG data modeling language used for network configuration and management protocols such as NETCONF.
-
D.
RFC 3339
RFC 3339 is an Internet standard that defines a simplified, unambiguous date and time format commonly used in internet protocols and data interchange.
-
E.
RFC 2119
RFC 2119 is an IETF document that defines the standard key words (like "MUST" and "SHOULD") used to indicate requirement levels in technical specifications.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa622b9fbc8190bff82acdde10deb6 |
completed | March 6, 2026, 5:12 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad680e8c908190a62a0a2f92a2b335 |
completed | March 8, 2026, 12:14 p.m. |
Created at: March 4, 2026, 7:28 p.m.