Triple
T25863828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Money |
E651556
|
entity |
| Predicate | historicallyBackedBy |
P178997
|
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: [Money, historicallyBackedBy, Gold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicallyBackedBy Context triple: [Money, historicallyBackedBy, Gold]
-
A.
historicallyBorneBy
Indicates that an entity has carried, possessed, or used another entity (such as a name, title, or symbol) at some point in the past.
-
B.
historicallyExtendedBy
Indicates that something has been continued, expanded, or carried forward over time by another, later entity or development.
-
C.
historicallyAdoptedBy
Indicates that something (such as a practice, policy, idea, or object) was used or taken up by an entity at some point in the past.
-
D.
historicallyBasedOn
Indicates that something is derived from, inspired by, or modeled on historical events, sources, or precedents.
-
E.
historicallyClaimedBy
Indicates that an entity has, at some point in the past, asserted ownership, control, or rights over another entity or territory.
- 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_69e7ab3a199c81909227cb964cacfe24 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f719cc31ec819099bebcf833b14d76 |
completed | May 3, 2026, 9:47 a.m. |
| PD | Predicate disambiguation | batch_69f71820c6c88190ab38b4fa626d22cc |
completed | May 3, 2026, 9:40 a.m. |
| PDg | Predicate description generation | batch_69f71995853c8190912025c0e83640c8 |
completed | May 3, 2026, 9:47 a.m. |
Created at: April 22, 2026, 8:06 a.m.