Triple
T10452839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Beaux' Stratagem |
E246473
|
entity |
| Predicate | isFrequentlyRevived |
P94122
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Beaux' Stratagem, isFrequentlyRevived, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyRevived Context triple: [The Beaux' Stratagem, isFrequentlyRevived, true]
-
A.
hasRevivalsIn
Indicates that something has been brought back, renewed, or reintroduced in specific times, places, or contexts.
-
B.
revivedAs
Indicates that an entity, after having ceased to exist or function in its original form, comes back into existence or operation in a new or restored form.
-
C.
periodOfRevival
Indicates a time span during which something that had declined or been inactive experiences renewed growth, activity, or prominence.
-
D.
revivedBy
Indicates that an entity has been brought back to life, consciousness, or active state through the action or intervention of another entity.
-
E.
revivedAtLevel
Indicates that an entity was brought back to life or reactivated when a specified level or stage was reached.
- F. None of above. chosen
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_69d381c04fe08190957c26c526a3b05a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4fe0d73d48190acb687b96918e0cf |
completed | April 7, 2026, 12:52 p.m. |
| PD | Predicate disambiguation | batch_69d4fb7d353c8190a73f439a956c7606 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe058fcc81909428137d9ffd6d90 |
completed | April 7, 2026, 12:52 p.m. |
Created at: April 6, 2026, 12:17 p.m.