Triple
T20067481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elmire |
E499645
|
entity |
| Predicate | usesStratagem |
P13064
|
FINISHED |
| Object | staged seduction scene |
—
|
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: staged seduction scene | Statement: [Elmire, usesStratagem, staged seduction scene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesStratagem Context triple: [Elmire, usesStratagem, staged seduction scene]
-
A.
usesStrategy
chosen
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
B.
tacticalFeatureUsed
Indicates that a specific tactical feature, maneuver, or capability is employed or brought into play within a tactical situation or operation.
-
C.
hasStrategicPass
Indicates that one entity possesses or controls a strategically important passage, route, or corridor relevant to another entity.
-
D.
usedAgainst
Indicates that one entity is employed, applied, or deployed in opposition to, or for the purpose of affecting, another entity.
-
E.
usesForces
Indicates that one entity applies physical, magical, or other types of forces to influence, move, or affect 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_69da627770948190997f486f9a2e370f |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66379f2cc81908f13a7b216878f12 |
completed | April 20, 2026, 5:33 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:39 p.m.