Triple
T33027461
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PASV |
E845079
|
entity |
| Predicate | responseCode |
P33257
|
FINISHED |
| Object | 227 |
—
|
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: 227 | Statement: [PASV, responseCode, 227]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responseCode Context triple: [PASV, responseCode, 227]
-
A.
usesResponseCode
chosen
Indicates that one entity produces, returns, or relies on a particular response code as part of its behavior or interaction.
-
B.
failureResponseCodeExample
Indicates the example HTTP status code that should be returned when the related operation fails.
-
C.
responseUnit
Indicates a unit or entity that provides or carries out a response in relation to another entity or event.
-
D.
responseTermination
Indicates that a response, process, or interaction has been brought to an end, either normally or due to some terminating condition.
-
E.
responseField
Indicates that a particular piece of information is included as part of a response or output structure.
- 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_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:23 a.m.