Triple
T29691623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bud Abbott |
E751224
|
entity |
| Predicate | roleInDuo |
P77541
|
FINISHED |
| Object | straight man |
—
|
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: straight man | Statement: [Bud Abbott, roleInDuo, straight man]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInDuo Context triple: [Bud Abbott, roleInDuo, straight man]
-
A.
roleInTheWay
Indicates that one entity is obstructing, hindering, or otherwise blocking another entity’s progress, action, or intended path.
-
B.
roleInDialogue
Indicates that an entity participates in a dialogue with a specific conversational role (e.g., speaker, listener, moderator) relative to other participants.
-
C.
roleInName
Indicates that a specific role, title, or position is included as part of an entity’s name or naming expression.
-
D.
bilateralRole
Indicates a relationship where each of two entities holds a defined role with respect to the other in a mutual or two-sided interaction.
-
E.
roleInRelationship
chosen
Indicates that an entity holds a specific role or position within a defined relationship between two or more entities.
- 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_69f0d625b09481909b0b69aea1e846c8 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff1ba8694481909ceb36f26ca85612 |
completed | May 9, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69ff1b27f0f08190a9e74308c5b3d1ba |
completed | May 9, 2026, 11:31 a.m. |
Created at: April 28, 2026, 7:17 p.m.