Triple
T500105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French Armed Forces |
E10380
|
entity |
| Predicate | abolishedConscription |
P9435
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [French Armed Forces, abolishedConscription, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abolishedConscription Context triple: [French Armed Forces, abolishedConscription, 2001]
-
A.
usesConscription
Indicates that a state or authority compels individuals into military or national service through mandatory conscription.
-
B.
demobilization
Indicates the process by which armed forces or combatants are formally released from military service and military structures are reduced or disbanded.
-
C.
abolishedConcept
chosen
Indicates that one entity has formally ended, eliminated, or done away with the other entity as a concept, practice, or institution.
-
D.
repealed
Indicates that a law, rule, or regulation has been officially revoked or annulled so that it no longer has legal effect.
-
E.
reasonForAbolition
Indicates the cause, justification, or circumstances that led to something being formally ended or abolished.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f13096248190a622a58dcf540b00 |
completed | Feb. 28, 2026, 1:44 p.m. |
| PD | Predicate disambiguation | batch_69a2edfbb7e0819092cf29c2c68fe8fb |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.