Triple
T33027693
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PWD |
E845085
|
entity |
| Predicate | hasReplyCode |
P33257
|
FINISHED |
| Object | 257 |
—
|
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: 257 | Statement: [PWD, hasReplyCode, 257]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReplyCode Context triple: [PWD, hasReplyCode, 257]
-
A.
hasReplyType
Indicates that an entity’s reply or response is of a specified type or category.
-
B.
usesResponseCode
chosen
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
C.
hasCommunicationCodeType
Indicates that an entity is associated with a specific type or category of communication code (e.g., phone, fax, email, messaging).
-
D.
hasReceiver
Indicates that an entity serves as the recipient or target of something provided, sent, or directed by another entity.
-
E.
hasResponderMessageCount
Indicates the number of messages sent by the responder in a given interaction or conversation.
- 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_69f34950749c8190ae05cd27adb16d58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a033d975d788190aafc4be10d6c5c1c |
completed | May 12, 2026, 2:47 p.m. |
| PD | Predicate disambiguation | batch_6a033cc2668481908cb696e57632a68f |
completed | May 12, 2026, 2:44 p.m. |
Created at: May 1, 2026, 1:23 a.m.