Triple
T20128032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Monk of Mokha |
E490807
|
entity |
| Predicate | hasPlaceInSeries |
P6115
|
FINISHED |
| Object | standalone work |
—
|
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: standalone work | Statement: [The Monk of Mokha, hasPlaceInSeries, standalone work]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlaceInSeries Context triple: [The Monk of Mokha, hasPlaceInSeries, standalone work]
-
A.
placeInSeries
chosen
Indicates the position or order that something occupies within a sequence or series.
-
B.
basedInSeries
Indicates that one entity is set, located, or primarily takes place within the narrative world or context of a particular series.
-
C.
hasPartOfSeriesPosition
Indicates that an entity occupies a specific position or order within a larger series or sequence.
-
D.
hasPlaceIn
Indicates that one entity occupies, is located within, or holds a specific position in another entity or context.
-
E.
significantPlaceInSeries
Indicates that a place plays an important or notable role within the context of a particular series.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6675fe3d48190b0c20b483a951e68 |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:31 p.m.