Triple
T33437652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leaflet |
E856271
|
entity |
| Predicate | hasVersioningSystem |
P9403
|
FINISHED |
| Object | semantic versioning |
—
|
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: semantic versioning | Statement: [Leaflet, hasVersioningSystem, semantic versioning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVersioningSystem Context triple: [Leaflet, hasVersioningSystem, semantic versioning]
-
A.
supportsVersioning
Indicates that the subject provides or is compatible with functionality for managing and maintaining multiple versions of an item or resource.
-
B.
usesVersionControlSystem
chosen
Indicates that an entity employs a version control system to manage and track changes to its files or code.
-
C.
hasVersionManager
Indicates that one entity is responsible for managing, controlling, or overseeing the versions or revisions of another entity.
-
D.
hasVersionStatus
Indicates that an entity is associated with a particular version state or status within its lifecycle or revision history.
-
E.
hasRevisionMechanism
Indicates that an entity is equipped with a mechanism or process for updating, modifying, or revising its content or state.
- 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_69f349709e7881908c342b4d34f555f4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f71fb1ab3881908e2f7c0e6f23db49 |
completed | May 3, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f71cc6397881909aaad37a9daa8a7e |
completed | May 3, 2026, 10 a.m. |
Created at: May 1, 2026, 1:36 a.m.