Triple
T36208939
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Admirable Crichton (1930 film) |
E1047481
|
entity |
| Predicate | originatesFromPlayBy |
P53243
|
FINISHED |
| Object | J. M. Barrie |
E62003
|
NE 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: J. M. Barrie | Statement: [The Admirable Crichton (1930 film), originatesFromPlayBy, J. M. Barrie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatesFromPlayBy Context triple: [The Admirable Crichton (1930 film), originatesFromPlayBy, J. M. Barrie]
-
A.
basedOnPlayBy
chosen
Indicates that something (typically a creative work) is derived or adapted from a play authored by a specified entity.
-
B.
originatedInShow
Indicates that something (such as a character, concept, or element) first appeared or was introduced in a particular show.
-
C.
performedPlayBy
Indicates that a theatrical play or performance was carried out or enacted by a particular person or group.
-
D.
playedFrom
Indicates that an action of playing (such as media playback or a performance) originated from a particular source or starting point.
-
E.
adaptedAsPlayBy
Indicates that a work has been transformed or reinterpreted into a play by a particular adapter.
- F. None of above.
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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39b41babbc819095b993b7bbb4211a |
completed | June 22, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.