Triple
T16648869
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Debenham |
E404547
|
entity |
| Predicate | modeOfIntroduction |
P52482
|
FINISHED |
| Object | passenger on the Taurus Express |
—
|
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: passenger on the Taurus Express | Statement: [Mary Debenham, modeOfIntroduction, passenger on the Taurus Express]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modeOfIntroduction Context triple: [Mary Debenham, modeOfIntroduction, passenger on the Taurus Express]
-
A.
oftenIntroducedBy
Indicates that one entity is frequently presented, mentioned, or brought into context by another entity.
-
B.
modeOfEmergence
Indicates the manner or process through which something comes into existence, develops, or arises.
-
C.
introducedVia
chosen
Indicates that one entity was brought to the attention, presence, or awareness of another entity through a specific intermediary, method, or channel.
-
D.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
E.
modeOfAcquisition
Indicates the method or process by which something is obtained, gained, or acquired.
- 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_69d8838a41f08190b0c3f79c47df5078 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e37ad794388190b2817d2ec5ff0de0 |
completed | April 18, 2026, 12:36 p.m. |
| PD | Predicate disambiguation | batch_69e319b1d7f08190b5ecb4a68c636c15 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:18 a.m.