Triple
T28231091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Private Moscow |
E711733
|
entity |
| Predicate | hasNarrativePace |
P73974
|
FINISHED |
| Object | fast-paced |
—
|
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: fast-paced | Statement: [Private Moscow, hasNarrativePace, fast-paced]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNarrativePace Context triple: [Private Moscow, hasNarrativePace, fast-paced]
-
A.
hasNarrative
Indicates that one entity contains, presents, or is associated with a story or narrative about another entity or subject.
-
B.
hasTenseNarrative
Indicates that a narrative is expressed using a specific grammatical tense or set of tenses.
-
C.
isFastPaced
chosen
Indicates that an activity, event, or process proceeds quickly with rapid progression and little downtime.
-
D.
isNarrativeDriven
Indicates that an entity’s primary structure or progression is guided by a storyline or plot rather than by mechanics, data, or other non-story elements.
-
E.
hasNarrativeToneOfWork
Indicates that a work exhibits or is characterized by a particular narrative tone.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fce28d6c3081908bf76f5db63ecf68 |
completed | May 7, 2026, 7:05 p.m. |
| PD | Predicate disambiguation | batch_69fce12d2f08819082134b5eb3db6a24 |
completed | May 7, 2026, 6:59 p.m. |
Created at: April 27, 2026, 10:52 p.m.