Triple
T5106346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Selby |
E115103
|
entity |
| Predicate | parliamentarianForcesIncluded |
P61598
|
FINISHED |
| Object | infantry |
—
|
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: infantry | Statement: [Battle of Selby, parliamentarianForcesIncluded, infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parliamentarianForcesIncluded Context triple: [Battle of Selby, parliamentarianForcesIncluded, infantry]
-
A.
ParliamentarianForceStrength
Indicates the magnitude or level of military or coercive power held or deployed by a parliamentary or legislature-aligned force in a given context.
-
B.
containsParliament
Indicates that one political or administrative entity includes a parliament within its structure or jurisdiction.
-
C.
ParliamentarianSide
Indicates that one entity is aligned with, represents, or belongs to the Parliamentarian side in a political or legislative context.
-
D.
parliamentaryInvolvement
Indicates involvement or participation of an entity in the activities, processes, or functions of a parliament or parliamentary body.
-
E.
parliamentComponents
Indicates that one entity is a component or constituent part of a parliamentary body.
- 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_69bd4440b3348190be1251fd8b7951f1 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd75a7c6748190b02b7c2b617c830f |
completed | March 20, 2026, 4:28 p.m. |
| PD | Predicate disambiguation | batch_69bd715fe3a8819087d3065adddba515 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd72e1b7cc8190b2e621fdf8f22e38 |
completed | March 20, 2026, 4:16 p.m. |
Created at: March 20, 2026, 1:41 p.m.