Triple
T24230159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French monetary reform of 1795 |
E601707
|
entity |
| Predicate | affectedInstrument |
P155281
|
FINISHED |
| Object | coinage |
—
|
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: coinage | Statement: [French monetary reform of 1795, affectedInstrument, coinage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: affectedInstrument Context triple: [French monetary reform of 1795, affectedInstrument, coinage]
-
A.
influencedInstrument
Indicates that one entity has affected, shaped, or altered a musical instrument or tool in some way, such as its design, use, style, or development.
-
B.
relatedToInstrument
Indicates a general relationship where one entity is connected or associated with a musical instrument.
-
C.
allowedInstrument
Indicates that a particular instrument is permitted or authorized for use in a given context or activity.
-
D.
appliesInstrument
Indicates that an agent performs an action using a specific instrument or tool as the means to carry out that action.
-
E.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
- 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_69e29538aafc8190a2386fdebbd1393b |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f287e3187c8190ab054ad983ed0335 |
completed | April 29, 2026, 10:36 p.m. |
| PD | Predicate disambiguation | batch_69f1c448abec8190b87cbf9ed419a309 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f1c6d4e99081909f61899eccafb73e |
completed | April 29, 2026, 8:52 a.m. |
Created at: April 18, 2026, 12:01 a.m.