Triple
T12663511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yet Do I Marvel |
E302484
|
entity |
| Predicate | firstPersonSpeaker |
P63735
|
FINISHED |
| Object | Black poet |
—
|
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: Black poet | Statement: [Yet Do I Marvel, firstPersonSpeaker, Black poet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPersonSpeaker Context triple: [Yet Do I Marvel, firstPersonSpeaker, Black poet]
-
A.
frontPerson
Indicates that one entity serves as the primary representative, leader, or public face positioned at the forefront in relation to another entity.
-
B.
primaryParticipant
Indicates that an entity plays the main or most central role in a given event, activity, or relationship.
-
C.
speaker2
Indicates that the referenced entity serves as the second speaker or interlocutor in a communicative interaction or dialogue.
-
D.
principalInterlocutor
chosen
Indicates that one entity serves as the main or primary conversational partner or speaker in an interaction with another entity.
-
E.
firstSpeechFocus
Indicates that the referenced entity is the primary or initial focus or topic of attention in a given speech or utterance.
- 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_69d7bded71a88190bb76e2413af9ea66 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617c5b888190b37d4ede139bb49e |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b78ce8819091f15dd5013e6da5 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:19 p.m.