Triple
T5402701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shylock |
E120816
|
entity |
| Predicate | demandsFrom |
P7686
|
FINISHED |
| Object | a pound of Antonio's flesh |
—
|
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: a pound of Antonio's flesh | Statement: [Shylock, demandsFrom, a pound of Antonio's flesh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demandsFrom Context triple: [Shylock, demandsFrom, a pound of Antonio's flesh]
-
A.
demands
chosen
Indicates that one entity insists that another entity provide something or take a specific action, typically with authority or urgency.
-
B.
demanded
Indicates that one entity forcefully or insistently requested something from another entity.
-
C.
demand
Indicates that one entity requests or insists that another entity provide something or perform an action, often with an expectation of compliance.
-
D.
requires
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
E.
requisitionedBy
Indicates that something has been formally requested or claimed for official use by a particular agent or authority.
- 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_69bd46391c0c81909fa484446732b6a3 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8932b8bc8190bd31e11b167a7212 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd84660ea08190a641084814fcf94d |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:04 p.m.