Triple
T7893232
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semantic Versioning specification |
E183286
|
entity |
| Predicate | specifiesFormat |
P77631
|
FINISHED |
| Object | MAJOR.MINOR.PATCH |
—
|
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: MAJOR.MINOR.PATCH | Statement: [Semantic Versioning specification, specifiesFormat, MAJOR.MINOR.PATCH]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesFormat Context triple: [Semantic Versioning specification, specifiesFormat, MAJOR.MINOR.PATCH]
-
A.
packageFormat
Indicates the format or type in which a package is structured, encoded, or delivered.
-
B.
handlesFormat
Indicates that an entity is capable of processing, interpreting, or otherwise working with a specified data or content format.
-
C.
overseesFormat
Indicates that one entity is responsible for supervising, managing, or controlling the format or formatting standards of another entity.
-
D.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
E.
serializationFormatFor
chosen
Indicates the data serialization format used to encode or represent a given resource or entity.
- 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_69ca828c474c8190a254d6499871eaff |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3a008fb88190a039fec40483ab93 |
completed | March 31, 2026, 3:05 a.m. |
| PD | Predicate disambiguation | batch_69cae92b0cd881908e715a10d3252e83 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5 p.m.