Triple
T6244413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Edward Hyde |
E139681
|
entity |
| Predicate | causeOfExistence |
P694
|
FINISHED |
| Object | potion created by Dr. Henry Jekyll |
—
|
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: potion created by Dr. Henry Jekyll | Statement: [Mr. Edward Hyde, causeOfExistence, potion created by Dr. Henry Jekyll]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: causeOfExistence Context triple: [Mr. Edward Hyde, causeOfExistence, potion created by Dr. Henry Jekyll]
-
A.
causeOf
chosen
Indicates that one entity brings about, produces, or is responsible for the occurrence or existence of another entity or event.
-
B.
proposesExistenceOf
Indicates that one entity puts forward or suggests that another entity should exist or be brought into existence.
-
C.
reasonForCreation
Indicates that one entity was created for the purpose, cause, or motivation specified by another entity.
-
D.
concludesExistenceOf
Indicates that one entity determines or infers that another entity exists.
-
E.
reasonForDemise
Indicates the cause, circumstance, or factor that led to an entity’s death or termination.
- 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0631c63d48190a41ec1232aecb373 |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:23 p.m.