Triple
T668659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French franc (Latin Monetary Union) |
E12922
|
entity |
| Predicate | metalStandard |
P1838
|
FINISHED |
| Object | gold |
—
|
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: gold | Statement: [French franc (Latin Monetary Union), metalStandard, gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metalStandard Context triple: [French franc (Latin Monetary Union), metalStandard, gold]
-
A.
stateMetal
Indicates that an entity is in a metallic state or exhibits properties characteristic of a metal.
-
B.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
-
C.
metallicity
Indicates the proportion of an object's mass that is made up of elements heavier than hydrogen and helium, typically used to describe the chemical richness of stars or galaxies.
-
D.
authorizedCoinMetal
chosen
Indicates that a particular metal is officially approved for use in minting a given coin.
-
E.
standardComposition
Indicates that one entity is composed or constructed according to a recognized or conventional standard defined by 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49ff921288190a2e5edb201ba69ee |
completed | March 1, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69a49d18942c819083b3d1887e505900 |
completed | March 1, 2026, 8:10 p.m. |
Created at: March 1, 2026, 7:36 p.m.