Triple
T929640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W3C Technical Reports |
E20060
|
entity |
| Predicate | identifierPattern |
P3732
|
FINISHED |
| Object | https://www.w3.org/TR/shortname/ |
—
|
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/shortname/ | Statement: [W3C Technical Reports, identifierPattern, https://www.w3.org/TR/shortname/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifierPattern Context triple: [W3C Technical Reports, identifierPattern, https://www.w3.org/TR/shortname/]
-
A.
notationPattern
Indicates a recurring way in which something is symbolically represented or written, such as a consistent style or structure of notation used for an entity or concept.
-
B.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
C.
fieldPattern
Indicates a recurring or structured arrangement or configuration present within a field or area.
-
D.
kitPattern
Indicates the design or visual pattern featured on a team's kit or uniform.
-
E.
locationPattern
Indicates a recurring or structured spatial relationship, where an entity consistently appears or is arranged in a particular type of location or spatial configuration.
- 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.