Triple
T14793723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quantum Fund |
E347719
|
entity |
| Predicate | usedStrategyInEvent |
P99450
|
FINISHED |
| Object | shorting the British pound in 1992 |
—
|
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: shorting the British pound in 1992 | Statement: [Quantum Fund, usedStrategyInEvent, shorting the British pound in 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedStrategyInEvent Context triple: [Quantum Fund, usedStrategyInEvent, shorting the British pound in 1992]
-
A.
usesStrategy
Indicates that an entity intentionally applies a particular strategy or method to achieve a goal or perform an action.
-
B.
usesTrainingStrategy
Indicates that one entity applies or follows a particular training strategy in carrying out its learning or optimization process.
-
C.
appliedInEvent
chosen
Indicates that an action, method, or concept is utilized or carried out within the context of a specific event.
-
D.
endUseEvent
Indicates an event marking the final or terminating use of something by an entity.
-
E.
usedInState
Indicates that something is employed, applied, or functions within a particular state or condition.
- 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_69d822ea8b7c819097dfadf3d45545e6 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decd5ec43c8190ad7a10a556519bb0 |
completed | April 14, 2026, 11:27 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:31 a.m.