Triple
T34894858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EUROGENDFOR |
E1006401
|
entity |
| Predicate | hasComponentForce |
P58250
|
FINISHED |
| Object | French Gendarmerie Nationale |
E62635
|
NE 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 Gendarmerie Nationale | Statement: [EUROGENDFOR, hasComponentForce, French Gendarmerie Nationale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasComponentForce Context triple: [EUROGENDFOR, hasComponentForce, French Gendarmerie Nationale]
-
A.
hasComponentForces
chosen
Indicates that a composite force is associated with, or can be decomposed into, specific component forces.
-
B.
hasDimensionForForce
Indicates that one entity specifies or defines the dimensional characteristics associated with a force-related quantity of another entity.
-
C.
componentForces
Indicates that a force is decomposed into its constituent directional components that together produce the original overall force.
-
D.
hasTypeOfForces
Indicates that one entity is associated with, or characterized by, a particular kind or category of forces.
-
E.
hasForceStrength
Indicates that one entity possesses a certain level or degree of physical or exerted force strength in relation to another entity or context.
- F. None of above.
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_69f76dbfe5788190ad8b64f241f470c8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37c61d45588190982d7a0e93ddb5b9 |
completed | June 21, 2026, 11:08 a.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.