Triple
T339165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian ruble (Empire) |
E6794
|
entity |
| Predicate | startUse |
P3267
|
FINISHED |
| Object | early modern period |
—
|
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: early modern period | Statement: [Russian ruble (Empire), startUse, early modern period]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startUse Context triple: [Russian ruble (Empire), startUse, early modern period]
-
A.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
B.
actualUse
Indicates that an entity is currently being used or utilized in practice, as opposed to being merely available, planned, or potential.
-
C.
operationStart
chosen
Indicates the point in time or event at which a specific operation or process begins.
-
D.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
E.
usedOn
Indicates that one entity is applied to, operated on, or otherwise utilized in relation to 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_69a2e79434908190a9d5afe415153ad9 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eae3a27c81909fc7deb600125fb1 |
completed | Feb. 28, 2026, 1:17 p.m. |
| PD | Predicate disambiguation | batch_69a2e95067e88190a914a1c1d0283dfc |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.