Triple
T3000611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romanian Armed Forces |
E81176
|
entity |
| Predicate | conscriptionAbolished |
P30300
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Romanian Armed Forces, conscriptionAbolished, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conscriptionAbolished Context triple: [Romanian Armed Forces, conscriptionAbolished, 2007]
-
A.
conscriptionTerm
Indicates the length or duration of mandatory military service imposed on individuals.
-
B.
usesConscription
Indicates that a state or authority compels individuals into military or national service through mandatory conscription.
-
C.
abolishedDuring
chosen
Indicates that an entity or practice ceased to exist or was officially ended within the time period defined by another entity.
-
D.
finalAbolition
Indicates the complete and permanent elimination of something, such that it no longer exists or is practiced in any form.
-
E.
demobilization
Indicates the process by which armed forces or combatants are formally released from military service and military structures are reduced or disbanded.
- 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_69ad8b187fc8819085914d3c9ea3142d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad9a1022e48190afee77db94635ff2 |
completed | March 8, 2026, 3:47 p.m. |
| PD | Predicate disambiguation | batch_69ad9615fefc8190ad96da92519cb7a3 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.