Triple
T23690879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poitevin |
E585292
|
entity |
| Predicate | currentlySpokenBy |
P153422
|
FINISHED |
| Object | mainly older generations |
—
|
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: mainly older generations | Statement: [Poitevin, currentlySpokenBy, mainly older generations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentlySpokenBy Context triple: [Poitevin, currentlySpokenBy, mainly older generations]
-
A.
spokenBy
Indicates that a particular utterance, statement, or piece of speech is produced or said by a specific entity.
-
B.
previouslyVoicedBy
Indicates that one entity served as the voice actor for another entity at some earlier time, but no longer does so in the current context.
-
C.
narratorPlayedBy
Indicates that a given narrator character is portrayed or voiced by a specific performer or actor.
-
D.
playedBy
Indicates that a role, character, or performance is portrayed or executed by a specific person or agent.
-
E.
portrayedBy
Indicates that one entity serves as the actor or performer who represents or plays the role of another entity in a work or medium.
- 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_69e249037ce0819088b149608e98f685 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b5c16af08190b2f4d126c60a7e75 |
completed | April 29, 2026, 7:39 a.m. |
| PD | Predicate disambiguation | batch_69f155d5265881908e43a9696b6a6d0f |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f157cc43a881909ed2d8b0a09b5d73 |
completed | April 29, 2026, 12:58 a.m. |
Created at: April 17, 2026, 6:52 p.m.