Triple
T7893224
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semantic Versioning specification |
E183286
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | SemVer |
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: SemVer | Statement: [Semantic Versioning specification, alsoKnownAs, SemVer]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SemVer Context triple: [Semantic Versioning specification, alsoKnownAs, SemVer]
-
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.
PEP 440
PEP 440 is the Python Packaging Authority’s standard that defines a consistent versioning scheme for Python packages.
-
C.
MXVER
MXVER is the UN/LOCODE identifier for the Port of Veracruz, a major maritime gateway on Mexico’s Gulf Coast.
-
D.
Subversion
Subversion is a centralized version control system used to manage and track changes to source code and other files in software development projects.
-
E.
Pro Git
Pro Git is a comprehensive, freely available book that serves as a widely used guide to the Git version control system for developers of all levels.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a008fb88190a039fec40483ab93 |
completed | March 31, 2026, 3:05 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5ba9c2ac8190b8faf1518390dff4 |
completed | March 31, 2026, 5:29 a.m. |
Created at: March 30, 2026, 5 p.m.