Triple
T34295343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Glorious First of June |
E880008
|
entity |
| Predicate | frenchPrisonersTaken |
P6764
|
FINISHED |
| Object | over 3,000 |
—
|
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: over 3,000 | Statement: [Battle of the Glorious First of June, frenchPrisonersTaken, over 3,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frenchPrisonersTaken Context triple: [Battle of the Glorious First of June, frenchPrisonersTaken, over 3,000]
-
A.
UnionPrisonersTaken
Indicates that Union forces captured and held individuals as prisoners.
-
B.
FrenchCasualties
Indicates that the relationship specifies the number or extent of casualties suffered by French forces in a given event or context.
-
C.
involvedFrenchTroops
Indicates that the event, action, or situation included the participation or presence of French military forces.
-
D.
frenchTroopsEvacuated
Indicates that French military forces withdrew or were removed from a particular location or situation.
-
E.
prisonersOfWar
chosen
Indicates a relationship where certain individuals are held in custody by an enemy during an armed conflict as prisoners of war.
- 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_69f349b79f6c81909cb468c92c39c74d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:57 a.m.