Triple
T36500284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Act IV of Much Ado About Nothing |
E899305
|
entity |
| Predicate | characterInvolved |
P200812
|
FINISHED |
| Object | Hero |
—
|
NE NERFINISHED |
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: Hero | Statement: [Act IV of Much Ado About Nothing, characterInvolved, Hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterInvolved Context triple: [Act IV of Much Ado About Nothing, characterInvolved, Hero]
-
A.
characterInvolvedIn
chosen
Indicates that a character participates in, is associated with, or plays a role in a particular event, action, or situation.
-
B.
involvedActor
Indicates that an entity participates as an actor or participant in the referenced event, activity, or situation.
-
C.
implicatedPerson
Indicates that a person is alleged or shown to be involved in, responsible for, or connected to a particular event, action, or wrongdoing.
-
D.
constantInvolved
Indicates that a constant participates in or is directly involved in the specified relation, operation, or context.
-
E.
crewInvolvedIn
Indicates that a crew (as a group or unit) participates in, contributes to, or is otherwise involved in a specified event, activity, or operation.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ffbb1c5bf88190a0bf791213045885 |
completed | May 9, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69ffba0ab0f881908f84ef81f7a1bfe8 |
completed | May 9, 2026, 10:49 p.m. |
Created at: May 3, 2026, 4:10 p.m.