Triple
T31401315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fru talman |
E801001
|
entity |
| Predicate | speechActRole |
P53328
|
FINISHED |
| Object | vocative expression |
—
|
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: vocative expression | Statement: [Fru talman, speechActRole, vocative expression]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speechActRole Context triple: [Fru talman, speechActRole, vocative expression]
-
A.
speechAct
Indicates that one entity performs a communicative action (such as stating, asking, commanding, or promising) directed toward another entity or audience.
-
B.
speakerRole
chosen
Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
-
C.
encodingRole
Indicates the role or function an entity has in the process of encoding information into a particular form or representation.
-
D.
roleInVox
Indicates that an entity holds a specific role or function within a Vox-related context, such as a project, system, or organization named or described as "Vox."
-
E.
actorRole
Indicates that an entity participates in an event or action in a specific capacity or function (such as performer, initiator, or responsible party).
- 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_69f224ea9998819086ae2e4f4f4091c8 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:19 p.m.