Triple
T6904851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States gold policy |
E159785
|
entity |
| Predicate | allowedPrivateGoldOwnershipFrom |
P38332
|
FINISHED |
| Object | 1975-01-01 |
—
|
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: 1975-01-01 | Statement: [United States gold policy, allowedPrivateGoldOwnershipFrom, 1975-01-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowedPrivateGoldOwnershipFrom Context triple: [United States gold policy, allowedPrivateGoldOwnershipFrom, 1975-01-01]
-
A.
canOwn
chosen
Indicates that one entity is permitted or legally able to possess or hold ownership rights over another entity.
-
B.
ownedIn
Indicates that one entity possesses or holds legal or recognized ownership of another entity within a specific context, domain, or scope.
-
C.
publiclyOwned
Indicates that an entity is owned or controlled by a government or public authority rather than by private individuals or organizations.
-
D.
authorizedCoinMetal
Indicates that a particular metal is officially approved for use in minting a given coin.
-
E.
ownedProperty
Indicates that one entity possesses legal ownership or control over another entity as property.
- 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_69c68839ccb88190b4aa5cc1aca3448f |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d989c13081908a2e346cde9e3a50 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:25 p.m.