Triple
T31036571
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GIS |
E790867
|
entity |
| Predicate | isGendarmerieUnit |
P171326
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [GIS, isGendarmerieUnit, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isGendarmerieUnit Context triple: [GIS, isGendarmerieUnit, true]
-
A.
isGendarmerieType
Indicates that an entity belongs to, or is classified as, a specific type or category within the gendarmerie (military police) organization.
-
B.
isAboutMilitaryUnit
Indicates that something (such as a document, statement, or resource) concerns, discusses, or pertains to a specific military unit.
-
C.
isNamedMilitaryUnit
Indicates that the subject is a military unit that has been given a specific official name.
-
D.
isMilitaryStaffOf
Indicates that one entity serves as military personnel working for, or assigned to, another entity (such as an organization, unit, or individual).
-
E.
stateMilitaryUnitOf
Indicates that a military unit is organized, controlled, or officially associated with a particular state or governmental 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69f80b62c8190bf2af2be0d3a7df8 |
completed | May 3, 2026, 1:06 a.m. |
| PD | Predicate disambiguation | batch_69f69d1a37e081908d1d86b90ff502bd |
completed | May 3, 2026, 12:55 a.m. |
| PDg | Predicate description generation | batch_69f69dfbf6ac8190ba2e6fc0adfd8b73 |
completed | May 3, 2026, 12:59 a.m. |
Created at: April 29, 2026, 8:59 p.m.