Triple
T2114446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NNTP |
E42573
|
entity |
| Predicate | responseCodeType |
P2202
|
FINISHED |
| Object | 3-digit numeric codes |
—
|
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: 3-digit numeric codes | Statement: [NNTP, responseCodeType, 3-digit numeric codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseCodeType Context triple: [NNTP, responseCodeType, 3-digit numeric codes]
-
A.
usesResponseCode
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
B.
resultType
Indicates the type or category of outcome that is produced by a given process, action, or operation.
-
C.
codeType
chosen
Indicates the classification or category assigned to a particular code within a coding or encoding system.
-
D.
typicalResponse
Indicates that an entity’s behavior, reaction, or outcome is the standard or commonly expected response in a given context or situation.
-
E.
hasCommunicationCodeType
Indicates that an entity is associated with a specific type or category of communication code (e.g., phone, fax, email, messaging).
- 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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbb05b51c81908a78c816f492c45c |
completed | March 7, 2026, 5:43 a.m. |
| PD | Predicate disambiguation | batch_69abb7ba08948190a3c236bb53ee4257 |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.