Triple
T7234676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Patay |
E155191
|
entity |
| Predicate | primaryArmFrench |
P70976
|
FINISHED |
| Object | heavy cavalry |
—
|
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 cavalry | Statement: [Battle of Patay, primaryArmFrench, heavy cavalry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryArmFrench Context triple: [Battle of Patay, primaryArmFrench, heavy cavalry]
-
A.
usesPrimaryFrenchGateway
Indicates that an entity routes its primary communications or connections through a main gateway located in or associated with French infrastructure or networks.
-
B.
FrenchUnit
chosen
Indicates that a unit or entity is associated with France, typically by origin, affiliation, or national identity.
-
C.
FrenchCommander
Indicates that an entity serves as a military commander associated with France.
-
D.
FrenchOperation
Indicates an operation, mission, or activity that is conducted by, under the authority of, or primarily involving France or French entities.
-
E.
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).
- 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_69c688143bfc81908d4176617735e601 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea552a688190a00f5d0ad982f787 |
completed | March 27, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69c6e7644648819096a5e2de5d0dbe97 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:55 p.m.