Triple
T3944589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neapolitan ducat |
E92114
|
entity |
| Predicate | monetaryHierarchy |
P52167
|
FINISHED |
| Object | higher-value coin |
—
|
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: higher-value coin | Statement: [Neapolitan ducat, monetaryHierarchy, higher-value coin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monetaryHierarchy Context triple: [Neapolitan ducat, monetaryHierarchy, higher-value coin]
-
A.
monetaryComponent
Indicates that something is a financial element or part of a larger monetary value, structure, or transaction.
-
B.
monetaryFunction
Indicates a relationship where something serves a financial role, such as handling, managing, or affecting money or economic value.
-
C.
monetarySystemType
Indicates the type or classification of a monetary system associated with an entity.
-
D.
monetarySystemRole
Indicates the role or function an entity has within a monetary system, such as issuing, regulating, or managing money and related instruments.
-
E.
definedMonetarySystem
Indicates that an authority or entity has established and specified the rules, structure, and characteristics of a particular monetary system.
- 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_69aed965502c8190904ebad1203a4ae8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1515c688190a38332aedeed8a76 |
completed | March 9, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_69aee764235081909309b3c982f322a9 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef14f9bb4819098e64b527b546d74 |
completed | March 9, 2026, 4:11 p.m. |
Created at: March 9, 2026, 3:24 p.m.