Triple
T23294034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Lansdowne |
E590112
|
entity |
| Predicate | ParliamentarianCasualties |
P151733
|
FINISHED |
| Object | heavy |
—
|
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: heavy | Statement: [Battle of Lansdowne, ParliamentarianCasualties, heavy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ParliamentarianCasualties Context triple: [Battle of Lansdowne, ParliamentarianCasualties, heavy]
-
A.
servedInParliament
Indicates that a person has held a position as a member of a parliamentary body during some period of time.
-
B.
hadParliamentaryRepresentationIn
Indicates that an entity was represented by one or more members in a specified parliament or legislative body during a given time or period.
-
C.
parliamentarianForcesIncluded
Indicates that certain forces or military units were part of, or included within, the parliamentarian forces.
-
D.
resultedInParliament
Indicates that one event, action, or situation caused or led to the formation, change, or outcome of a specific parliament.
-
E.
containsParliament
Indicates that one political or administrative entity includes a parliament within its structure or jurisdiction.
- 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_69e25d1af9d88190a0b9b5e8fa608618 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196cdce7081908ca1cf9107b87f61 |
completed | April 29, 2026, 5:27 a.m. |
| PD | Predicate disambiguation | batch_69effcf325f88190b320268c3c551abb |
completed | April 28, 2026, 12:18 a.m. |
| PDg | Predicate description generation | batch_69f01d88b4ec8190a2a17a88e0eda178 |
completed | April 28, 2026, 2:38 a.m. |
Created at: April 17, 2026, 5:02 p.m.