Triple
T32512401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Larry |
E830970
|
entity |
| Predicate | speakingRole |
P9564
|
FINISHED |
| Object | rare |
—
|
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: rare | Statement: [Larry, speakingRole, rare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: speakingRole Context triple: [Larry, speakingRole, rare]
-
A.
speakerRole
Indicates the functional role or capacity in which an entity is acting as a speaker within a communicative event.
-
B.
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."
-
C.
roleInTheVoices
Indicates that an entity has a specific role or participation in the production or performance of "The Voices."
-
D.
audienceRole
Indicates the role or function an entity has as part of an audience in relation to another entity or event.
-
E.
roleInDialogue
chosen
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
- 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_69f3492318348190ba37fb6b5f1d67f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c49fc3248190809b0d61ac1b1b1a |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1 a.m.