Triple
T2850748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Battle of Bull Run |
E63084
|
entity |
| Predicate | strengthUnionApprox |
P26187
|
FINISHED |
| Object | 62000 |
—
|
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: 62000 | Statement: [Second Battle of Bull Run, strengthUnionApprox, 62000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: strengthUnionApprox Context triple: [Second Battle of Bull Run, strengthUnionApprox, 62000]
-
A.
unionStrengthApproximate
chosen
Indicates that the strength of a union or combination between entities is represented in an estimated or approximate manner rather than as an exact value.
-
B.
unionStrength
Indicates the degree of solidarity, cohesion, or collective power within or among unions or union members.
-
C.
strengthensFrom
Indicates that one entity becomes stronger, more effective, or more intense as a result of influence, support, or input from another entity.
-
D.
UnionStrength
Indicates the degree of solidarity, cohesion, and collective bargaining power within or among unions in a given context.
-
E.
forceSizeUnion
Indicates that the combined size or extent of multiple entities is being constrained or determined as a single unified whole.
- 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_69ab4c407c408190857d25e027155ce9 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf437328819098506ec8a3a23e11 |
completed | March 7, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69abdd0e86808190bcefffafbd3cd441 |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.