Triple
T4046629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CSS Box Alignment Module |
E84080
|
entity |
| Predicate | w3cTRURL |
P47307
|
FINISHED |
| Object | https://www.w3.org/TR/css-align-3/ |
—
|
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: https://www.w3.org/TR/css-align-3/ | Statement: [CSS Box Alignment Module, w3cTRURL, https://www.w3.org/TR/css-align-3/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: w3cTRURL Context triple: [CSS Box Alignment Module, w3cTRURL, https://www.w3.org/TR/css-align-3/]
-
A.
typicalURIForm
Indicates that one entity is the standard or canonical URI form typically used to represent another entity.
-
B.
URLPattern
Indicates that a resource or endpoint is identified or matched by a specific structured web address pattern.
-
C.
namespaceURI
Indicates the URI that defines the namespace to which a given identifier, element, or resource belongs.
-
D.
accessURL
Indicates the web address or endpoint through which a resource can be accessed or retrieved.
-
E.
hasReferenceURL
chosen
Indicates that an entity is associated with a specific web address that serves as a reference or source of additional information about it.
- 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_69aed930bd5c819083e7dcc14fc44f69 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb62593c8190ab8462c4d9cd9d08 |
completed | March 9, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69aef900386481909d04555a9ec9b0e3 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:37 p.m.