Triple
T3628594
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strepsiades |
E76898
|
entity |
| Predicate | takesAction |
P9769
|
FINISHED |
| Object | burns the Thinkery (in some versions of the play) |
—
|
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: burns the Thinkery (in some versions of the play) | Statement: [Strepsiades, takesAction, burns the Thinkery (in some versions of the play)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: takesAction Context triple: [Strepsiades, takesAction, burns the Thinkery (in some versions of the play)]
-
A.
actsOn
chosen
Indicates that one entity performs an action that affects, targets, or is directed toward another entity.
-
B.
takes
Indicates that one entity receives, accepts, or comes into possession of another entity.
-
C.
canTakeActionWith
Indicates that one entity is able or permitted to perform an action jointly or in coordination with another entity.
-
D.
fromAct
Indicates that an entity originates from, is produced by, or results from a specified action or event.
-
E.
causeOfAction
Indicates that one entity is the reason or basis for initiating a legal action or lawsuit against another entity.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2df2b708190afef6925a53ec551 |
completed | March 8, 2026, 6:41 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.