Triple
T29503816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Basic |
E748454
|
entity |
| Predicate | statusCodeUsedForChallenge |
P33257
|
FINISHED |
| Object | 401 Unauthorized |
—
|
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: 401 Unauthorized | Statement: [Basic, statusCodeUsedForChallenge, 401 Unauthorized]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusCodeUsedForChallenge Context triple: [Basic, statusCodeUsedForChallenge, 401 Unauthorized]
-
A.
issuedChallengeFor
Indicates that one entity has formally presented or posed a challenge for another entity to undertake or respond to.
-
B.
hasBeenChallengedFor
Indicates that an entity has been formally questioned, disputed, or contested specifically in relation to another entity or issue.
-
C.
statusInHTTP3
Indicates the HTTP/3 protocol status or condition associated with a given resource, request, or connection.
-
D.
stateActionChallenged
Indicates that an action taken by a state (or state authority) has been formally disputed, questioned, or contested by another party.
-
E.
usesResponseCode
chosen
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
- 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_69f0bd455a9c8190b40a3e8ea38cf61f |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fd553d7cb881908d243e7a9f30ac85 |
completed | May 8, 2026, 3:15 a.m. |
| PD | Predicate disambiguation | batch_69fd514dcb1c81908333c70d7edd79c9 |
completed | May 8, 2026, 2:58 a.m. |
Created at: April 28, 2026, 4:26 p.m.