Triple
T6715153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Ballinamuck |
E153247
|
entity |
| Predicate | FrenchOutcome |
P72831
|
FINISHED |
| Object | French forces surrendered |
—
|
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: French forces surrendered | Statement: [Battle of Ballinamuck, FrenchOutcome, French forces surrendered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FrenchOutcome Context triple: [Battle of Ballinamuck, FrenchOutcome, French forces surrendered]
-
A.
FrenchObjective
Indicates that an entity serves as the goal, target, or object of an action or relation specifically within a French linguistic or contextual framework.
-
B.
FrenchRole
Indicates a role or position that an entity holds specifically within a French context (e.g., in France or related to French institutions, culture, or language).
-
C.
FrenchOperation
Indicates an operation, mission, or activity that is conducted by, under the authority of, or primarily involving France or French entities.
-
D.
FrenchCommander
Indicates that an entity serves as a military commander associated with France.
-
E.
effectOnFrance
Indicates the impact, influence, or consequences that something has on France.
- 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_69c68809b4608190a2509ddb5ab87f05 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d1246b748190aed94e8ab8625f7e |
completed | March 27, 2026, 6:49 p.m. |
| PD | Predicate disambiguation | batch_69c6d08c5d348190a29dee668c398e70 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d11fab808190b18160ff3829fcc6 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:07 p.m.