Triple
T7893233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Semantic Versioning specification |
E183286
|
entity |
| Predicate | specifiesComponent |
P55139
|
FINISHED |
| Object | MAJOR version |
—
|
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 version | Statement: [Semantic Versioning specification, specifiesComponent, MAJOR version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: specifiesComponent Context triple: [Semantic Versioning specification, specifiesComponent, MAJOR version]
-
A.
definesComponent
chosen
Indicates that one entity specifies or establishes the structure, behavior, or characteristics of another entity as its component.
-
B.
component1
Indicates that one entity functions as a constituent or part of another entity within a larger whole.
-
C.
componentType
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
D.
developsComponentFor
Indicates that one entity creates or builds a component intended to be used by or within another entity.
-
E.
componentFrom
Indicates that one entity is derived from, produced by, or originates as a component of another 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.