Triple
T31873977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Moto’s Gamble |
E813686
|
entity |
| Predicate | followsNarrativeFormula |
P194368
|
FINISHED |
| Object | detective mystery |
—
|
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: detective mystery | Statement: [Mr. Moto’s Gamble, followsNarrativeFormula, detective mystery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsNarrativeFormula Context triple: [Mr. Moto’s Gamble, followsNarrativeFormula, detective mystery]
-
A.
narrativeFormat
Indicates the specific structural or stylistic form in which a narrative is presented or expressed.
-
B.
followsNarrativeArchetype
chosen
Indicates that one entity’s structure, development, or progression conforms to a recognized narrative archetype or story pattern established by another.
-
C.
narrativeStrategy
Indicates the method or approach used to structure, present, or convey a story or sequence of events.
-
D.
narrativeSequence
Indicates that one event or narrative element follows another in a temporal or logical storytelling order.
-
E.
narratesWith
Indicates that one entity tells, recounts, or presents a story, event, or information in conjunction with or alongside another entity.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fdbaa226708190b8ed96e93aad38de |
completed | May 8, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69fdb58b07e48190837e00966de050d4 |
completed | May 8, 2026, 10:06 a.m. |
Created at: April 30, 2026, 11:55 p.m.