Triple
T20415618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Petruchio |
E500703
|
entity |
| Predicate | criticalDiscussionTopic |
P51889
|
FINISHED |
| Object | gender roles in Shakespeare |
—
|
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: gender roles in Shakespeare | Statement: [Petruchio, criticalDiscussionTopic, gender roles in Shakespeare]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criticalDiscussionTopic Context triple: [Petruchio, criticalDiscussionTopic, gender roles in Shakespeare]
-
A.
discussed
chosen
Indicates that one entity talked about, examined, or debated a topic, issue, or other entity with someone else.
-
B.
discussionPublic
Indicates that a discussion is accessible to the general public rather than being restricted or private.
-
C.
discourse
Indicates that one entity engages in extended verbal or written communication or discussion with another entity.
-
D.
criticalApproach
Indicates that an entity employs an analytical, questioning, or evaluative method toward another entity, concept, or work.
-
E.
inAcademicDebate
Indicates that one entity is engaged in a formal, scholarly argument or discussion with another entity, typically following academic norms and methods of reasoning.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a437eec8190a20c89a236dd5bc0 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5766df0008190a73c4f613c29678f |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.