Triple
T10822875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Port Republic |
E255418
|
entity |
| Predicate | unionPrisonersTakenApprox |
P13732
|
FINISHED |
| Object | about 450 |
—
|
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 450 | Statement: [Battle of Port Republic, unionPrisonersTakenApprox, about 450]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unionPrisonersTakenApprox Context triple: [Battle of Port Republic, unionPrisonersTakenApprox, about 450]
-
A.
UnionPrisonersTaken
Indicates that Union forces captured and held individuals as prisoners.
-
B.
estimatedPrisoners
Indicates a relationship where a value represents the estimated number of prisoners associated with a particular entity or context.
-
C.
numberOfPrisonersApproximate
chosen
Indicates an approximate count of prisoners associated with an entity or situation, rather than an exact number.
-
D.
AustrianPrisonersTakenApproximate
Indicates that an approximate number of Austrian prisoners were taken or captured in a given context or event.
-
E.
estimatedPrisonerCount
Indicates the estimated number of prisoners associated with a particular context, such as a location, time period, or event.
- 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_69d6aa8081448190a9324184f2bd1c26 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7344c551c8190a7491d468b8a4a04 |
completed | April 9, 2026, 5:08 a.m. |
| PD | Predicate disambiguation | batch_69d70d1bf3648190b36fa96ea018e0dc |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:18 p.m.