Triple
T13089985
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Second Manassas |
E310435
|
entity |
| Predicate | forceUnionApproximate |
P38271
|
FINISHED |
| Object | about 62,000 troops |
—
|
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: about 62,000 troops | Statement: [Second Manassas, forceUnionApproximate, about 62,000 troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceUnionApproximate Context triple: [Second Manassas, forceUnionApproximate, about 62,000 troops]
-
A.
forceSizeUnion
chosen
Indicates that the combined size or extent of multiple entities is being constrained or determined as a single unified whole.
-
B.
effectOnUnion
Indicates the impact or influence that something has on a union as a whole.
-
C.
unionStrengthApproximate
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.
-
D.
endedUnionBetween
Indicates that one entity caused or marked the termination of a union, alliance, or partnership with another entity.
-
E.
formedByUnionOf
Indicates that something is created or defined as the union or combination of multiple other things.
- 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d98138a1d481908a139f2f67eb3472 |
completed | April 10, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:03 p.m.