Triple
T10032298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | If-None-Match |
E204878
|
entity |
| Predicate | wildcardSemantics |
P48655
|
FINISHED |
| Object | * matches any current representation |
—
|
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: * matches any current representation | Statement: [If-None-Match, wildcardSemantics, * matches any current representation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wildcardSemantics Context triple: [If-None-Match, wildcardSemantics, * matches any current representation]
-
A.
wildCardContext
Indicates that the relationship or action occurs within a flexible, unspecified, or catch‑all contextual scope rather than a narrowly defined one.
-
B.
includesWildForm
Indicates that something contains or encompasses a wild or non-domesticated form of another entity.
-
C.
supportsPartialMatch
chosen
Indicates that the relationship or operation allows matching based on a subset or portion of the target criteria rather than requiring a complete or exact match.
-
D.
wildCardBerth
Indicates that an entity receives a berth or qualification through a wildcard allocation rather than through standard qualification criteria.
-
E.
supportsMultipleMatches
Indicates that the relationship or operation can involve or return more than one matching counterpart rather than being limited to a single match.
- 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_69ca834d77188190ad645e33e8ca3200 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdce461d6481908cc8f968856e0337 |
completed | April 2, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69cd4b8638508190b22acc65500ec7d6 |
completed | April 1, 2026, 4:44 p.m. |
Created at: March 30, 2026, 8:54 p.m.