Triple
T26482128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C CSS Validation Service |
E664715
|
entity |
| Predicate | backendLibrary |
P84822
|
FINISHED |
| Object | Jigsaw components |
—
|
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: Jigsaw components | Statement: [W3C CSS Validation Service, backendLibrary, Jigsaw components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: backendLibrary Context triple: [W3C CSS Validation Service, backendLibrary, Jigsaw components]
-
A.
backendExtension
Indicates that one entity functions as an extension or add-on to another entity’s backend system or service.
-
B.
relatedLibrary
Indicates that one library has a meaningful connection or association with another library, such as dependency, compatibility, or functional similarity.
-
C.
backendTarget
chosen
Indicates that one entity serves as the backend system, service, or endpoint that another entity connects to or depends on for processing or functionality.
-
D.
isMainLibraryOf
Indicates that a library serves as the primary or central library for a given organization, system, or collection.
-
E.
libraryFile
Indicates that one entity is a file that is part of, stored in, or managed by a particular library.
- 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_69ee883bc85481909885f92415cbce33 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f612fbdb1c8190a837de40747d6b53 |
completed | May 2, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69f602d5c8808190a1fdbebd6f0981e8 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 12:28 a.m.