Triple
T5899664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biff Loman |
E131188
|
entity |
| Predicate | stageMedium |
P67214
|
FINISHED |
| Object | drama |
—
|
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: drama | Statement: [Biff Loman, stageMedium, drama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stageMedium Context triple: [Biff Loman, stageMedium, drama]
-
A.
medium
Indicates that an entity serves as the means, channel, or intermediary through which an action, communication, or effect is carried out between other entities.
-
B.
stratotypeMedium
Indicates the type of material or medium (e.g., rock, sediment) that serves as the reference standard for a stratigraphic unit or stratotype.
-
C.
stageOf
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
D.
mediumCategory
Indicates the classification of an item or content according to the type or form of medium it belongs to (e.g., print, digital, audio, video).
-
E.
plannedMedium
Indicates that a particular medium or channel has been designated in advance for use in carrying out an action or communication.
- F. None of above. chosen
Provenance (4 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0334dc8248190b7394dcece362d52 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c0400dbec08190b2ef73689b2c0c31 |
completed | March 22, 2026, 7:16 p.m. |
Created at: March 22, 2026, 3:58 p.m.