Triple
T20818830
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Murdoch |
E512515
|
entity |
| Predicate | abilityOrigin |
P30515
|
FINISHED |
| Object | experiments by The Strangers |
—
|
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: experiments by The Strangers | Statement: [John Murdoch, abilityOrigin, experiments by The Strangers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abilityOrigin Context triple: [John Murdoch, abilityOrigin, experiments by The Strangers]
-
A.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
B.
originAssociatedWith
chosen
Indicates a relationship where an entity is connected to, derived from, or influenced by a particular origin, source, or point of beginning.
-
C.
agreementOrigin
Indicates that an agreement originates from, is derived from, or is based on a specified source or prior arrangement.
-
D.
registrationOrigin
Indicates the source or context from which a registration event was initiated or created.
-
E.
physicalOrigin
Indicates that one entity is the place or source from which another entity physically originates or comes into existence.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f5b1e08190a9c26f76bd544b68 |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.