Triple
T24783058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City Watch novels |
E620051
|
entity |
| Predicate | inUniverseChronologyNote |
P34213
|
FINISHED |
| Object | span multiple periods in Ankh-Morpork history |
—
|
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: span multiple periods in Ankh-Morpork history | Statement: [City Watch novels, inUniverseChronologyNote, span multiple periods in Ankh-Morpork history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseChronologyNote Context triple: [City Watch novels, inUniverseChronologyNote, span multiple periods in Ankh-Morpork history]
-
A.
chronologyNote
chosen
Indicates a note that explains or clarifies the temporal order, dating, or sequence of related events or records.
-
B.
inUniverseHistory
Indicates that an event, fact, or narrative element occurs within the fictional universe’s own internal timeline or recorded history, rather than in real-world or out-of-universe context.
-
C.
notedForInUniverse
Indicates that an entity is recognized or distinguished for a particular trait, role, or achievement within a specific fictional universe or narrative continuity.
-
D.
chronologyUsedBy
Indicates that a particular system, method, or scheme of chronological ordering is employed or adopted by a given entity.
-
E.
chronologyIn
Indicates that one event or temporal entity occurs within the chronological scope or timeframe defined by another.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:45 a.m.