Triple
T38231887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CAE |
E1013510
|
entity |
| Predicate | speakingTestFormat |
P190189
|
FINISHED |
| Object | face-to-face interview |
—
|
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: face-to-face interview | Statement: [CAE, speakingTestFormat, face-to-face interview]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speakingTestFormat Context triple: [CAE, speakingTestFormat, face-to-face interview]
-
A.
dialogueFormat
Indicates the specific structure or style in which a dialogue or conversational exchange is presented or encoded between entities.
-
B.
speechType
Indicates the specific category or form of spoken or written communication that an utterance or speech act belongs to (e.g., question, statement, command).
-
C.
coachedFormat
Indicates that one entity served as a coach or trainer to another entity in a particular format, style, or structured context.
-
D.
isSpoken
Indicates that a language or utterance is produced orally by a speaker or used in spoken form within a given context.
-
E.
trialFormat
Indicates the specific structure, rules, or procedural setup under which a trial or experimental process is conducted.
- F. None of above. chosen
Provenance (4 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
| PDg | Predicate description generation | batch_69fcc330b4288190858b49d986160706 |
completed | May 7, 2026, 4:52 p.m. |
Created at: May 3, 2026, 4:30 p.m.