Triple
T14009101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rupee |
E337029
|
entity |
| Predicate | historicalMaterial |
P112143
|
FINISHED |
| Object | silver |
—
|
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: silver | Statement: [rupee, historicalMaterial, silver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalMaterial Context triple: [rupee, historicalMaterial, silver]
-
A.
historicalEvidence
Indicates that there exists documented or otherwise verifiable information supporting the occurrence, authenticity, or truth of a past event, state, or relationship between entities.
-
B.
historicalPaper
Indicates that a paper has significant historical importance or impact within its field or context.
-
C.
historical
Indicates that the subject has existed, occurred, or been relevant in the past rather than in the present or future.
-
D.
historicalReference
Indicates that one entity refers to, cites, or alludes to another entity from an earlier time or historical context.
-
E.
historicalMedium
Indicates that an entity was conveyed, recorded, or expressed through a particular medium or format in its original historical context.
- 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_69d81c645c5c8190b1fd16a285a1b78a |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2ed44f90819099ad08c09c066b56 |
completed | April 14, 2026, 12:11 p.m. |
| PD | Predicate disambiguation | batch_69dd465dfbc4819090d8c61fd572d35f |
completed | April 13, 2026, 7:39 p.m. |
| PDg | Predicate description generation | batch_69de01ed2098819088ec45069f6f2609 |
completed | April 14, 2026, 8:59 a.m. |
Created at: April 9, 2026, 10:19 p.m.