Triple
T929638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C Technical Reports |
E20060
|
entity |
| Predicate | versioningPolicy |
P7002
|
FINISHED |
| Object | dated URIs for specific versions |
—
|
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: dated URIs for specific versions | Statement: [W3C Technical Reports, versioningPolicy, dated URIs for specific versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: versioningPolicy Context triple: [W3C Technical Reports, versioningPolicy, dated URIs for specific versions]
-
A.
versioningModel
Indicates that one entity serves as a versioning or revision-control model governing how versions of another entity are created, tracked, and managed.
-
B.
currentVersionDefinedIn
Indicates that the current or active version of an entity is specified or established within a particular source, document, or context.
-
C.
hasVersionNumber
Indicates that an entity is associated with a specific version identifier or number.
-
D.
hasUpdatePolicy
chosen
Indicates that one entity defines or is associated with the rules or strategy governing how another entity is updated or maintained over time.
-
E.
hasVersionCount
Indicates the total number of distinct versions associated with a given 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_69a493af3dc48190adb7263e6e445ea1 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b349b3d0819090c58b4fb60c6a1b |
completed | March 1, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69a4b29876348190a29f4ff9878074a5 |
completed | March 1, 2026, 9:41 p.m. |
Created at: March 1, 2026, 7:40 p.m.