Triple
T20223352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demetrius |
E495313
|
entity |
| Predicate | bodyUsedAs |
P126429
|
FINISHED |
| Object | ingredient in pie served to Tamora |
—
|
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: ingredient in pie served to Tamora | Statement: [Demetrius, bodyUsedAs, ingredient in pie served to Tamora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bodyUsedAs Context triple: [Demetrius, bodyUsedAs, ingredient in pie served to Tamora]
-
A.
usesBody
Indicates that one entity employs or utilizes the physical body of another (or its own) as a means or instrument to perform an action or function.
-
B.
bodyDisposedIn
Indicates that a body (typically a dead organism or corpse) is placed, discarded, or otherwise disposed of within a particular location or container.
-
C.
usesBodyPart
Indicates that an entity performs an action or function by employing a specific body part as a means or tool.
-
D.
bodyDisposedBy
Indicates that a body is disposed of, handled, or gotten rid of by a particular agent or entity.
-
E.
objectUsed
chosen
Indicates that one entity is used as a tool, instrument, or resource in performing an action involving 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd827708190b798a30f4e7d533f |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.