Triple
T14852638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Normandie‑Niémen Regiment |
E349267
|
entity |
| Predicate | approximateSorties |
P115871
|
FINISHED |
| Object | more than 5,000 combat sorties |
—
|
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: more than 5,000 combat sorties | Statement: [Normandie‑Niémen Regiment, approximateSorties, more than 5,000 combat sorties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateSorties Context triple: [Normandie‑Niémen Regiment, approximateSorties, more than 5,000 combat sorties]
-
A.
dailySorties
Indicates the number of missions or operations carried out per day by an entity.
-
B.
sorties
Indicates that an entity carries out or participates in a mission or operational deployment, typically involving a single trip or operation from a base and back.
-
C.
hasFlownSorties
Indicates that an entity has completed one or more operational flight missions (sorties).
-
D.
airStrikes
Indicates that one party conducts aerial attacks, typically using aircraft or drones, against a target or opposing party.
-
E.
estimatedAerialVictories
Indicates an approximate count of aerial combat victories attributed to an entity, rather than an exact, confirmed total.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded441e70881909bbf62b66d932aff |
completed | April 14, 2026, 11:56 p.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:54 a.m.