Triple
T31347723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 5e Régiment du génie de combat |
E799494
|
entity |
| Predicate | garrisonLanguage |
P171262
|
FINISHED |
| Object | French |
—
|
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 | Statement: [5e Régiment du génie de combat, garrisonLanguage, French]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: garrisonLanguage Context triple: [5e Régiment du génie de combat, garrisonLanguage, French]
-
A.
garrisonIncluded
Indicates that a particular garrison is included within, or forms part of, a specified larger military force, unit, or installation.
-
B.
garrisonType
Indicates the specific kind or classification of military garrison associated with an entity.
-
C.
garrisonOrigin
Indicates that a garrison or stationed military force originates from, or was initially formed in, a specified location or source.
-
D.
garrisonCommander
Indicates that one entity serves as the commanding officer in charge of the military garrison located at or associated with another entity.
-
E.
garrisonDevelopedBy
Indicates that a garrison is created, established, or developed by a specific agent or organization.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f19a79c81909647d8eef6706e44 |
completed | May 3, 2026, 1:04 a.m. |
| PD | Predicate disambiguation | batch_69f69d1d25e88190a7f57d323574da90 |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69ea761848190acb31298e65b7892 |
completed | May 3, 2026, 1:02 a.m. |
Created at: April 29, 2026, 9:17 p.m.