Triple
T3708032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azerbaijan SSR administrative divisions |
E80939
|
entity |
| Predicate | appliedInPeriod |
P47439
|
FINISHED |
| Object | Soviet era |
—
|
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: Soviet era | Statement: [Azerbaijan SSR administrative divisions, appliedInPeriod, Soviet era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appliedInPeriod Context triple: [Azerbaijan SSR administrative divisions, appliedInPeriod, Soviet era]
-
A.
appliedSince
Indicates that a particular condition, rule, status, or action has been in effect starting from a specified point in time and continues from that date onward.
-
B.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
C.
inForceInPeriod
chosen
Indicates that something (such as a rule, contract, or condition) is valid, applicable, or legally effective during a specified time period.
-
D.
timePeriodWithin
Indicates that one time period is entirely contained within the bounds of another time period.
-
E.
commonInPeriod
Indicates that something frequently occurs, appears, or is prevalent during a specified time period.
- 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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adc580b08481908391283778d5ce14 |
completed | March 8, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69adc041a8608190a2d543dab6d2ef6c |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:33 p.m.