Triple
T20977196
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MACH-IV questionnaire |
E516655
|
entity |
| Predicate | hasResponseType |
P92192
|
FINISHED |
| Object | self-report |
—
|
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: self-report | Statement: [MACH-IV questionnaire, hasResponseType, self-report]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResponseType Context triple: [MACH-IV questionnaire, hasResponseType, self-report]
-
A.
hasReplyType
chosen
Indicates that an entity’s reply or response is of a specified type or category.
-
B.
hasAnswerType
Indicates that a question or query is associated with a specific type or category of expected answer.
-
C.
typeOfResponse
Indicates the specific kind or category of reply or reaction that is given in response to a preceding action, event, or input.
-
D.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
-
E.
hasGoodType
Indicates that an entity possesses a type or classification considered appropriate, valid, or of high quality according to some defined criteria.
- 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_69e0b4fee5ac8190875fa9ceba1a5e5e |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fba4a0dc819083b90795d26adfff |
completed | April 21, 2026, 4:23 a.m. |
| PD | Predicate disambiguation | batch_69e5dbe6976081908abd4e9c8734bae9 |
completed | April 20, 2026, 7:55 a.m. |
Created at: April 16, 2026, 1:47 p.m.