Triple
T23653642
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Contades |
E584232
|
entity |
| Predicate | militarySphere |
P17742
|
FINISHED |
| Object | French armed forces |
—
|
NE NERFINISHED |
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 armed forces | Statement: [House of Contades, militarySphere, French armed forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militarySphere Context triple: [House of Contades, militarySphere, French armed forces]
-
A.
militaryDomain
chosen
Indicates that the relationship or action occurs within, pertains to, or is specifically associated with the military sphere or context.
-
B.
countryMilitary
Indicates that a country possesses, controls, or is associated with a particular military force or armed organization.
-
C.
militarySection
Indicates that one entity is a specific branch, division, or section within a larger military organization or force.
-
D.
militaryIssue
Indicates that one entity formally provides or distributes military-related items, orders, or directives to another entity.
-
E.
militarySystem
Indicates a relationship where an entity functions as, belongs to, or is characterized by a particular military organizational or operational system.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b3599128819092b6a44779889a78 |
completed | April 29, 2026, 7:29 a.m. |
| PD | Predicate disambiguation | batch_69f118d7903c8190bb590a71771e93af |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:49 p.m.