Triple
T2617861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederate States dollar |
E58932
|
entity |
| Predicate | finalValue |
P42237
|
FINISHED |
| Object | virtually worthless at end of war |
—
|
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: virtually worthless at end of war | Statement: [Confederate States dollar, finalValue, virtually worthless at end of war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalValue Context triple: [Confederate States dollar, finalValue, virtually worthless at end of war]
-
A.
finalStep
Indicates that an action or state represents the last step or concluding stage in a process or sequence.
-
B.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
finalHomeOf
Indicates that a location is the last or ultimate home, residence, or resting place of an entity.
-
D.
finalPassing
Indicates that an entity successfully completes or passes a final evaluation, test, or stage in a process.
-
E.
finalDisposition
Indicates the ultimate outcome, status, or resolution assigned to an entity after all relevant processes or decisions are complete.
- 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_69ab4ac444dc819099614e534dd6021f |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abdaca581881908fe8d3d820f839b7 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd80f48888190afdf7e3e042157d0 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abdac82b688190886a6ec2d6e2abc7 |
completed | March 7, 2026, 7:59 a.m. |
Created at: March 6, 2026, 9:50 p.m.