Triple
T1190188
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Vicksburg |
E25339
|
entity |
| Predicate | unionStrengthApproximate |
P26187
|
FINISHED |
| Object | 70000 |
—
|
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: 70000 | Statement: [Siege of Vicksburg, unionStrengthApproximate, 70000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionStrengthApproximate Context triple: [Siege of Vicksburg, unionStrengthApproximate, 70000]
-
A.
UnionStrength
Indicates the degree of solidarity, cohesion, and collective bargaining power within or among unions in a given context.
-
B.
union
Indicates that two or more sets are combined into a single set containing all elements that belong to at least one of them.
-
C.
laborUnion
Indicates that an entity is a labor union representing workers in collective employment-related matters.
-
D.
estimatedStrength
Indicates that a value represents an approximate or inferred level, magnitude, or intensity of something rather than a precisely measured strength.
-
E.
coalitionPotential
Indicates the potential or likelihood that two or more entities can form a cooperative alliance or coalition.
- 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_69a49427d98881908646d6c63b8cea1e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd58d8d88190b8d9c9c9de7f4e97 |
completed | March 1, 2026, 10:27 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5bacc481909e8dfd5215e4711a |
completed | March 1, 2026, 10:19 p.m. |
| PDg | Predicate description generation | batch_69a4bd0ab5f88190bb583fc63b4cc150 |
completed | March 1, 2026, 10:26 p.m. |
Created at: March 1, 2026, 7:45 p.m.